>Again you are mixing 2 incompatible ideas. Embedded data (general fields) are really yesterday's technology. They were used before ole automation. What it is designed is a quick link between nondbf data and the application to use that nondbf data. Automating tasks in embedded fields can only be done through keyboard commands and macros. The better approach is to move the data out of the general field (more reliable anyway as you don't have to depend on the integrity of the fpt field) and use ole automation on separate files. You can store the name of the files in a dbf table and get the same effect as an embedded field.
>
>Is that clearer?

Brings me to the same point, however. If it is yesterday's technology then there must be a better way that offers the same features. I don't know of a better way; perhaps someone else knows of one and can assist me on this one. I want users to be able to interact w/ the information embedded (not having to open another application and switch windows and such) ESP, I want to be able to display a word file (preferably w/ a scroll bar) driven by a grid listing of reports on the file.

I also want to be able to manipulate the data that is embedded. I don't see much alternative to embedding the data as there are 86228 reports currently in the DOS version of the file that takes up over 1.5 gig. This file is currently a text representation of a WP file and a PKZIP'd Word Perfect file. also a filename, a date and an internal Company file number. Many of these will have very similar if not the same name and even if we weren't still limited to the 8.3 (Novell 3.11, we are moving to NT as soon as this DOS->VFP port is complete) we still could not expect the user to have a different name for every single report. Especially since most of the reports are outsourced to typists and they name the file. We then load the disk into the system (usually 10 or so reports per disk).

even if we standardized on filenames, it would be a mess and would be far from foolproof.

The WORD manual implies that you CAN automate embedded data, but it doesn't really tell you how (other than activating the Word.Basic object via the application object, and then it makes some reference to making sure that the embedded object is first activated. Neither the Excel example nor the VB example give a clue as to what will work with VFP)


Is there another approach that I am missing that will not kill our file system, strain our users or otherwise make the DOS version more feasible??? Perhaps there is a USENET group that might be more suited to this discussion? All ideas and pointers will be greatly appreciated, I am at an empass right now.