For example, not having to hard code the virtual directory name to bring up the pdf. The code automatically knows where it's running from (oProp.ScriptPath) so it should be able to figure out where the generated PDfs are stored. Same with data, html, etc..

>Claude,
>
>>>(Part of the challenge is making it a portable solution, so that it can be moved and just work without any hard-coding or required directory structures..)
>
>I'v sent hmm... maybe a year ago a modified activeVFP2.11 where "required directory structures" was solved (directories was parameterized for the web page generation). Ah but maybe this isn't what you mean in this time but when web pages are done you can move them without regenerating them?
>
>AT