>The scenario:
>I have a simple form that uses the DataEnvironment for the tables. I create an .EXE and put it into a production directory that has it's own matching .DBC and tables. But the .EXE always refers back to the development directory's tables. I've done this before, but can't possibly understand how!

Yes this is a real problem with VFP, but there are ways around it. When you add a table to the DE of a form, VFP stores a relative path from the form to the DBC/DBF. This is not obvious because when you look at the database/cursorsource property however you will see an absolute path. As long as your form and DBC/DBF can be attached with a relative path (i.e. they are on the same drive) you can move from your test to your production environment with no problems. However, as you have said you have done it before O.K., what I guess may have happened with your situation, at some point VFP has stored an absolute path in your DE. What you have to do is this:
Open the form as a table with USE myform.scx
Browse on the table and open the properties memo field.
Scroll through the table looking for a Database or Cursorsource property that has an absolute path.
Replace the absolute path with a relative path.

This should fix you problem. That is until you want the user to specify the location of the data, or you want to store the data on a different drive! :-)

Darrel