>>>>A client has moved an old FPDOS 2.6 app from an old computer to a new one. The app includes FoxFire (version 3, I think) for DOS. The app works OK, except when they run a report they get a LOCFILE() dialog asking where LOAD.DBF is. If they manually find that file, the report runs fine.
>>>>
>>>>I seem to recall that FoxFire may make use of DOS environment variables to be able to find its components. Can anyone confirm this, and possibly let me know what the environment variable names are and what they do?
>>>>
>>>>The old computer is not easily accessible.
>>>
>>>I have a complete copy of Version 3.0.
>>>
>>>I ran a search for load.dbf on the drive it's located on.....not found.
>>>
>>>I ran a search of a project that uses it......not found.
>>>
>>>It looks like it is not a FoxFire distributed file.
>>>
>>>I would analyze the individual report designs that are having problems, if it's just one or two reports.
>>>
>>>If all FoxFire reports are behaving this way, I don't have a clue.
>>
>>Can you tell if there are any DOS environment variables that may be related to FoxFire? Wild guess, they may be named something like FF_Path etc.
>>
>>You can view environment variables by starting a CMD window (Start...Run...cmd), then typing SET at the prompt.
>
>No. Nothing like that.
>
>I did look at my FoxFire vers. 2.5 for DOS manual and a bright light appeared overhead. My long term memory recalls a file named ddereg.exe. It may have been missed when installing on a different computer.
>
>Here's a link: http://www.tek-tips.com/viewthread.cfm?qid=1358386&page=29

Hmm, thank you. We'll check into that.