This one drives me crazy! When you drop a table in a database in the form DE the absolute path to the database is stored as a property of the cursor. If the path exists when the applicaion is run, it will use that database no matter what the users path is set to. In our development environment, all of our projects are on a network drive mapped as P: This drive is mapped automatically for me by a logon script. I can log on to a users machine, and becasue the P drive exists, I end up using test data, where they use live data because they won't have a P drive and their path is set to live data in the config file. Try renaming the test data folder and see if that fixes the problem. If so, I would recommend using one of the examples the others mentioned to set the database path before the tables are opened.

John

>Alright, I am currently in programmer purgatory. It has been tasked of me to modify a project that was developed by someone else. Bad blood prevents us from consulting with the original programmer. His vastly different programming style from mine means he didn't do much of anything the way I would have done it, and I am having problems figuring some things out.
>
>The big issue is data location. When I compile, the resulting executable reads data from a test location, not the location of the real data (or of the database that is in the project). I cannot, for the life of me, figure out what is telling the program to look in this location. (If it were me, I would have had a public variable in the main program file, but no such luck here.) What really gets me is that I've checked out the forms and I can't find anything in the BeforeOpenTables method. How can somebody have a variable data location and not use BeforeOpenTables?!
>
>I'm just at a total loss of where to look here. I've even used the Windows file search feature to find the test path in any of the files in the project directory. No dice.
>
>Btw, I've been programming in FoxPro for over seven years (in amongst other kinds of projects), so I know my way around a FoxPro project reasonably well...though clearly not this FoxPro project. I don't know whether to feel humbled or angry.
>
>Does anyone have any ideas about where I should look? Thanks for any help in advance. I know this is not an easy question to answer.