Hi, Evan. I think you're describing a problem I had early on when I split used one project as a basis for another client. The second project includes a lot of forms and classes from the first, and when I compiled the 2nd EXE it used the first's data. The solution, for me, was to create the EXE (Save to) during the build in the directory for the first (aka parent application) directory. That way, the forms, etc. get compiled with relative pathes.

HTH.

>Hi folks. I am using VFP3.0b for Windows.
>
>One of my forms is giving me an error when I move it (in an exe) to a the 'live' directory.
>
>The form points back to the database, view and tables in the test directory. When I 'USE' the form, the properties for the cursors and view are only relative and not absolute ( database\schedule.dbf and not p:\db\main\database\schedule.dbf), so that seems okay. If I open the form in the form designer and look at the properties of the tables (cursors) and views in the dataenvironment, the properities are disabled and they show the complete path to the table as if it is hard-coded.
>
>So my questions is ... How can I ensure that the forms do not reference any data (databases, tables, views) incorrectly?