Hi Nirav,

This case study makes lot of things clear.

Just a simple solution with + perspective.

As you have a path to your Word Documents, Why not to create a hyperlink from Crystal to that MS Word document. It works gr8 and you never have to bother about any updates in Word Files even if it happens.

i hope that works.

Aashish


>My apologies if I'm not being detailed enough, but it is a rather complex situation, and I didn't want to give extra information to confuse the matter.
>
>What we're doing is that we currently use Crystal to print out our insurance policies. The first couple of pages have complex calculations, but the last 40 or so pages are mainly just pages of text (Word docs) that are embedded in the RPT by OLE. The problem with this approach is that there is no history of what a policy looked like in the past. It is important, for legal reasons, for us to be able to recreate what was sent to the customer in the past.
>
>The solution was to catalog all documents into the database and let the software decide which ones should be included. But, the first few pages of the printout still need to remain in Crystal because of the calculations involved, so we were going to have a subreport to another RPT that prints out the correct 40 or so pages of text. That is why Crystal needs to be involved.
>
>The issue is that although I can store a LINK to the Word doc in a GENERAL field of a table, a Crystal report based on that General field will not honor that link. In other words, changes made to the original document will not be reflected in the Crystal report unless the document is reappended into the General field. This is not too big of a deal, because ideally, changes should not be made to the documents once they are published anyway.
>
>The other thing is that I was wondering if there was another approach I could take so that I wouldn't have to store the document in the General field at all (since I have the path already). That's where I'm unable to find an answer, so as of right now, I'm just going to include the docs in the database in a General field.
>
>Thanks for your help, Aashish. I hope all that made sense. :)