>Hello,
>
>I have an application that we are moving from vfp5 to vfp6. For testing purposes, we have a development area, which has a copy of the production area tables.
>
>When I open up the "production" area manager, and use the database container for the production area, and I can go in and look at the tables and see that they are pointing and residing in the production area, but when I try and run the program from the manager, or create an executable, it always uses the development data.
>
>You all were such a wonderful help with my first problem, I wanted to see if you could help me with this..... Actually, that isn't true - I know someone out there can help me with this.... <grin>
>
>Thanks ahead of time....
>
>Jeff Lovin

It seems to be common problem: VFP DataEnvironment stores hard-coded paths to the tables/database you use in development environment. The common remedy is to reset DE.Cursor.Database properties in run-time:
***DE.BeforeOpenTables event
Thisform.SetAll("Database",cDataPathName,"Cursor") && it works if you don't have free tables in DE