>>>Does anyone have any comments about rules for using database tables from
>>>different directories? In this application a directory may reside on the
>>>local PC, but the data path may be on a server, either one might have a
>>>directory designation determined by the user.
>>
>>Form.DataEnvironment.BeforeOpenTable events should call app method resetting DataEnvironment.CursorX.Database properties.
>
>Hi Jeff:
>In one of my vfp applications, I have a menu option that says..
>SET DATA PATH...If you click on this option, a FORM (Called GET_DATA)
>opens and you can set a valid data path by filling out a text field.
>The code I use for this is in the click event of the OK button on GET_DATA.
>HTH...thanks ...rob :)
>if !empty(thisform.text1.value)
> store alltrim(thisform.text1.value) to mypath
> newpath = mypath+"\my_database_name"
> if file(newpath+".dbc")
> set path to &mypath
> else
> messagebox('Can not find Data Files from - '+mypath,'Problem')
> thisform.text1.setfocus
> return
> endif
>endif

This is a good idea, but still doesn't deal with the form's hardcoded paths in the DE. I think that a combination of the two methods suggested above. Procedures allowing the end user to choose the data location should only be used with known COMPETENT users. As most of us know, this is very difficult to ascertain. A better solution would be to specify a program to run after the initial install that would prompt for the location of the data and store the result to a location table that would be accessed by the program from then on.