Hi,
Thank you for your enquiry.
Files viewed through a DocView object are not embedded in the published executable, but are instead copied over to the publication directory during publishing and given a numerical filename (such as 00000000.txt) to prevent end-users from immediately identifying which resource corresponds to which file.
By default, the resource resides in the root publication directory (at the same level as the published executable). If you do not want resources in the publication directory, you would need to use a system variable when setting up the DocView object. For example, if you open the properties of the DocView object and set the path to the file as:
<SYSTEM_PUBLICATION_DIR>\Resources\test.txt
This will tell the publication to look within the directory from which it is running (which will obviously be the root of the CD when distributed) and try to find a folder named 'Resources'. If found, the publication will then look in this folder for a file named 'test.txt'. If found, the contents of this file will be displayed in the DocView object.
By the way, it is not necessary to use a DocView object to view text files, and I would perhaps recommend adding a normal Text object to the page, then opening the properties of this object, selecting the Text tab and enabling the 'Automatically read in this disk file' option. You can now browse to the text file you wish to display, then apply the changes and preview. The benefits of using a text object are that you will not see the bevelled border which affects DocView objects, the publication will not need to generate an ILMOle.dll file and the text should display noticeably quicker than when using DocView (as the text object does not need to communicate with the OLE engine).
I hope this helps. Please do not hesitate to contact me if you have any further queries.
Kind regards,
_________________ Robin Garrett
Digital Workshop Technical Support
|