Hi, Art.

So that you can receive the benefit of all the experience here, here's a copy of your email follow up to me:

>Nancy - Thanks very much for taking the time to reply to my question.
>I'm really looking to install my application on various user's machines
>in the SAME location (C:\somedirectory), but the database itself may
>reside on various drives (depending on how the user's PCs are connected
>to the net) -- even though they are the same physical files. In other
>words, my drive J: and someone else's drive H: will point to the same
>physical data; the application will be on drive c: in both cases.

>Any ideas on that one?? If so, GREAT! If not, thanks very much anyway. I
>learned something I didn't know (the '%s' argument - NEAT!), and I truly
>appreciate your taking the time to help out a FoxPro beginner!!

...snip

This is absolutely doable. You'll want use the UNC path rather than the mapping to point to the data. I'm sure there must be many different ways to implement the rest of it. I have one application that is installed in one directory and might run on one of two (or more) subdirectories of data. So when the app starts it asks the user which set of data they want and then uses SET DEFAULT TO to that dir. Pretty simple, but the concept applies.

HTH

p.s. The paths of the data are not "hard-linked" to the project. But their relative path is noted in the forms, for example. The only really care I take is to make sure _relative_ pathing is consistent.

>>I'm having no trouble working in the project manager and using the data environment to progam local, stand alone applications. However, I need to be able to have the end user specify what drive and directory the (shared) data will be on at run time. Now, I'm new to FoxPro, but it seems to me that the location of the tables is hard-linked to the project.