>VFP looks FIRST at the hard-coded path which is saved in the data-environment. Second in the current directory and third in the path. This can cause major problems when you move an EXE from test to production directories.

This seems silly to me. How often is the development path the same as the run-time path? As long as it doesn't complain that the hard-coded directory doesn't exist, I should be ok.

>Biggest problem isn't OPENING tables, but making sure form1 doesn't close tables that form2 needs. That's one VERY good reason to use private datasessions.

The way our app is set up, it's rare that more than one table is open at a time. The main situation is that form one has a button that calls up form two, and you stay on form two until your done with it, then close it and go back to form one. For instance, I have a form that lists the client information with all their trips in a grid. There are so many fields in the trip table that a grid isn't practical for entering and viewing the data. So I put just enough fields in the grid that you can tell which trip is which. To see the trip in detail, you click on it, then click a button, and another form comes up with all the trip info.

>Michelle, you're PUTM. Do a search on the word 'datasession'. You'll come up with several recent threads that have discussed these options in detail. You'll probably get the most information that way.

Maybe I'm getting things confused, but I don't think I need a datasession. I don't want form two to have a different record pointer than form one. Form two is just like "zooming in" to see more detail on something that is general on the main form.

Thanks,