Since you are using drive letters like F:. H:. and I:, is this in a networking environment? If so, what network? If this is netware, and the drive mappings are not MAP ROOT, there IS a difference between including that leading backslash or not, they will not necessarily refer to the same thing. On my local desktop I just did an example based on your code:

SET DEFAULT TO C:\
USE \appdir\table

and it worked just fine. OK, I just did the same test to one of my network drives (NT 4.0 server) and it worked fine, all combinations (using the backslas in the SET DEFAULT, not using it, using the leading backslash in the OPEN, not using it). Seems to work any way I try it, both in the command window and in a program. I am running VFP7 SP1 under XP Pro, NT 4.0 server for a file server.

HTH,
Randy

>I am using VFP 7.0 SP1 and just came accross a pathing problem with VFP 7.0 that doesn't occur in 6.0.
>
>We have three main servers, one for source code (I:), test data (H:) and production data (F:). I normally use the following code in my main *.prg so that I can run a program directly from development without compiling between each change:
>
>IF SYS(5) = 'I:'
>____SET DEFA TO 'I: \ DEVELOPMENT'
>____SET PATH TO 'DATA, LIBS, REPORTS, PROGS, H:'
>ELSE
>____SET DEFA TO 'F:'
>____SET PATH TO
>ENDIF
>
>Later in my project I open [H: \ SUBDIR \ MYTABLE.DBF] with the following code:
>
>USE \ SUBDIR \ MYTABLE
>
>Which works fine in VFP 6.0. I've used this in hundreds of programs. It will not work in VFP 7.0 unless I exclude the first backslash:
>
>USE SUBDIR \ MYTABLE
>
>It doesn't matter if I set path to [H:] or [H:\] it still doesn't like the first backslash. Am I missing something? I can't go back and change every occurence of this so my legacy code will run in VFP 7.0.
>
>TIA,