I do not think this is a compile issue. Tables in your DE will have the relative path stored along with the table name. If you open your form as a table and look at the properties for your cursors, you will see the path stored there. You can write some cleanup code to strip these paths and run it prior to compiling. Same thing for icons and pictures [relative path stored].

>I have a form with several table in my data environment. Typically, I compile my project and have VFP write the executable to my development environment. From there I will move the .EXE into a production environment with the necessary databases and tables. This works well.
>
>However, if I compile the project and have VFP write the .EXE directly to my production environment, the forms in the new .EXE (which have tables loaded in there data environments) will access the database and tables in my development environment instead of the ones supplied in the production environment.
>
>My pathing appears to be correct as I am not hard coding any pathing that would affect compiling. Furthermore, I can compile successfully to my development environment, copy the .EXE to the production environment and correctly access the live data in production.
>
>Has anybody run into this compiling issue before? Any help of suggestions would be appreciated. Is there another catagory I should be addressing this thread to?
>
>Tim