>>I have a prg that calls a form in
>>G:\psi12.0\custom
>>Before running the report form I want to change the
>>directory back to g:\psi12.0
>>Once there I want to call the report form in the G:\psi12.0\custom
>>folder then after the report is run set it back to the G:\psi12.0\custom
>>
>>so I want to back the folder up to ".."
>>and then call the report form "\custom\report.frx"
>>then set default back to: SYS(5)+SYS(2003)+"\custom"
>>The problem is I don't know the correct syntax to back the directory up one
>>and the call there report in the current folder + custom
>>
>>I am running this in a application that I did not create and it has a menu list that allows for custom reports. When I run a report to preview the app needs to verify a time and date stamp on a file in g:\psi12.0\system folder. If a user keeps the preview open for a while they get and error "can not verify time and date stamp on \system\bdefault.dbf.
>>
>>If I call the report from the folder one back from \custom I believe this
>>error will go away as the app will be in it's root folder and able to find the
>>system folder from there
>>
>>
>>
>>Any help would be greatly appreciated
>
>I don't see any reasons to jump between folders like that.
>Of course don't know your application logic.
>
>

>lcCurrentFolder = ADDBS(SYS(5)+CURDIR())
>cd ..
>REPORT FORM (lcCurrentFolder+[whatever name report has])
>cd (lcCurrentFolder)
>

Thanks.
I agree. I do not think I should have to do this. the application states
that the custom report menu is an isolated environment but this that were the case then why is their app checking the date of the file in the system folder.
when running the custom program the app assumes it is running from their root folder. To keep things clean and not ahve to dump 770 files into that root folder which I did not want to do. So I made a custom folder under their root folder to keep this a little cleaner. I a previous version of this application it worked perfectly. Now in the current version preview reports generate this error.