Hi Jason ----

Marty gave you good advice for working with General fields and OLE Bound controls. I would add that you may wish to consider using Automation to handle document management and *not* bind them via an OLE control. You table can then just store the pathname to the DOC files. If you want to open a particular document:

Assumption:

New field = cdocument.docpathname

Code to open a document:

cGetThisDoc = cdocument.docpathname
oMyDoc=CREATEOBJECT("Word.Application")
oMyDoc.Documents.Open(cGetThisDoc)
oMyDoc.Visible=.T.


>
>I have created a table to hold documents, appropriately called DOCUMENTS. I want to be able to have a user access word documents from FoxPro. So, I created this table with the following fields:
>
>ndocument_id (Pkey)
>cdocument_name
>cdocument_category
>cdocument_region
>cdocument_description
>gdocument_image
>
>_____________________
>
>The field I set up to access these documents is the gdoc._image field. I set it up with a "general" data type. Is that correct?
>
>My questions are:
>1. How do I link the documents to the table, versus embedding them?
>
>2. When creating a form for the interface, do I use unbound or bound OLE object? I am not sure what the difference is between the two.
>
>Thank you for any assistance in advance
>
>Jason