>I'm using VFP 6.0 My program works great if I execute it from the FoxPro Command Window. But once I built the exe I've run into some bugs.
>
>Bug #1: it seems when I call certain forms TALK somehow gets turned on. The only time I reference TALK is in the beginning where I explicitly turn it off. How could this happen?
>

SET TALK is scoped to the Data Session. If you use private datasessions, you have to SET TALK OFF in each of them.

>Bug #2: I've moved my application and database files to another directory. (k:\launcher\run) In one specific routine, I open a database which happens to belong to a container and I get the dialog box
>
>Open Table
>k:\launcher\invoices.dbc: Cannot link table
>k:\launcher\run\summary.dbf to this database:
>duplicate or missing fields. Would you like to locate the owning database or delete the link (and free the table)?
>
>Choices: Locate, Delete, Cancel
>
>My data files are in the same directory as my program. When opened the file I made no reference to the absolute location of the database, I just issued a USE SUMMARY. So there should be no reason for it to look in my source directory.

You have an absolute path reference in the DBC rather than a relative reference, create when you added the table to the DBC; as a result, it's using the absolute reference to try to open the file. The solution is to fix the entries in the DBC. You can download a tool to help fix the problem from here on UT; it's called the Database Relocation Wizard in the File Section under Visual Foxpro In General; there are distinct versions for VFP5 and VFP6.