We have this problem with Tables and Classes also. Some of our solutions involve pre-setting the Default Drive and Path with calls like:

Set Defa to Sys(5)
Set Path to Sys(2003)
OR...
Set Path to Fullpath('')

Also, the DE will not 'burn in' a Drive letter unless your Data is on another volume; it will use Minimal pathing to find the Table, Database, etc...

Another helpful item is to attach a ProjectHook object to your project and set current Path to the Application's Home directory when opening the PJX.

HTH,

-Irv.


>Not so much a question – more an observation that may help others avoid a difficult to find bug I recently encountered.
>
>When using APPEND FROM to add a set of records from table B to the end of table A, I found I was getting an incorrect set added. I had both tables open at the same time and the FOR condition applied to table B as a BROWSE achieved the correct subset of results. However, when applying the FOR condition to the APPEND FROM a different set of results was being passed across to table A.
>
>I discovered that the APPEND FROM will always search for table B along the default path. APPEND FROM ignored the fact that I already had the intended table B open. I had an old version of table B higher up the search path than the one currently open and this one had spurious records some of which met the FOR criteria and were being added to table A.
>
>You can avoid this trap by specifying the full path to table B or making sure that you only have a single instance of the file in the search path (which most folk will!).
>
>Barry