I like to use DE to design and set up tables, relations, etc. and it is advertised to open tables faster according to the documentarion. VFP uses a Minimum-pathing scheme so if your data is on the same drive as the EXE, then the path will be relative, as in:

..\DATA\Database1.dbc

...this means you can copy it anywhere and as long as the relative path from the EXE to the data remains unchanged, you're OK. A problem arisis if your EXE is on another logical drive, away from the data, then VFP is forced to 'burn in' the drive-letter:

H:\Myapp\Data\Database1.dbc

HTH,

-Irv.


>Hi again...
>When you design and create your VFP program, you set up diferent directories for all the parts of the proyect, that is for example: c:\SINFO for the main prgs, c:\SINFO\FORMS for all the forms, c:\SINFO\CLASSES for classes, and c:\SINFO\DATA for the database. When in the dessign proccess you create your forms and set its data enviroment to certain tables of the c:\SINFO\DATA\SINFO.dbc. In the main prg you open the c:\SINFO\DATA\SINFO.dbc, no problem at this time. But if for any reasson you decide to change the name of your data directory to c:\SINFO\DATADBC\SINFO.dbc so you change the Open dbc command of the main prg and it opens the right database but all the forms still trying to open its tables in the original directory. I looked at the properties window of the form´s cursors and it shows in the DataBase property the original directory and it seems to be read only. So in the future when you distribute the application it will be in all the clients desktops but the database will
>be in another computer (server) so the directory will be something like \\juanpc\c\SINFO\DATA\SINFO.dbc insted of C:\SINFO\DATA\SINFO.dbc
>How to fix this?
>
>Thanks Juan Uribe