>>Our actual SET PATH command for this application is:
>>

>>set path to ;
>>	data, menus, rptforms, reports, ;
>>	rptPrgs, ;
>>	vcx\forms, vcx\managers, vcx\controls, vcx\schedule, ;
>>	.\forms, .\prgs, .\cRpts, .\other, c:\vCTEMP, e:\vctemp, ;
>>	\sf\sdt\dbcx, \sf\sdt\source, \sf\sdt, ;
>>	.\vvc\FORMS, .\vvc\vcx\managers, .\vvc\vcx\forms, .\vvc\vcx\controls, ;
>>	.\work, .\nitejob, .\sports
>>

>>We can't set it to a hard-coded path, we need the path to be relative (for other reasons beyond reporting).
>>
>>Unfortunately, this application was developed without a compiled EXE. The users run a .PRG, which launches the menu, etc.
>>
>>Again, my problem is that *during* the report output, Adobe switches the default directory. I can set it before the output, and I can re-set it after. My problem is that it changes in the middle of the REPORT FORM... command.
>>
>
>Since we can't change the way the Adobe switches the directory we have to see what we can do to get VFP to find the files. We used to use relative pathing in our apps but changed it to be like
>
>

>lc_path = FULLPATH('data') + ", " + FULLPATH('menus') + ", " + ;
>          FULLPATH('reports') + ", " + FULLPATH('rptprgs') + ", " + ;
>          FULLPATH('vcx\forms') .. ect.
>
>SET PATH TO &lc_path.
>

>
>This allowed us to not hard code drive letters but still get the fullpath.
>
>If you need relative pathing you could
>lc_savpat = SET('PATH')
>Then parse out the relative pathing and do the fullpathing like I did above then after the report has run
>SET PATH TO &lc_savpat.

That would be nice if you could set the path to something longer than 1,023 characters. Since we can't we're stuck using relative pathing. Otherwise our clients could never run the app from a location such as "F:\ThisNetworkPath\MyApplicationFolder\ApplicationNumber1234567890".

Thanks for the ideas, anyway. Any other suggestions?

- George