>So I'm finally putting out my .exe in VFP9 (had been in VFP8) and have a bizarre bug relating to now you see it, now you don't data. This problem only shows up in the compiled .exe, not in the development environment.
>
>From Form A (no data buffering) I'm adding a record directly to a table (in a database) and then calling a modal form B to edit that record directly, without table buffering. Then, when the user closes Form B, the control returns to the calling form A.

>The data at this point is there, I can browse the table from VFP and it looks good and it is showing properly in a listbox on Form A.

By "browse the table from VFP" do you mean you can start another completely separate instance of VFP and verify that the data have been written there?

>Then, when I close form A the data that was previously there, is now reverted back to the original default values (mostly empty). Again, this only happens in the .exe, not in development. Both forms use private DE's.
>
>Tables/database are in good shape according to Abri Recover.

My first guess would be a pathing issue of some kind - do you have more than 1 copy of the table/database in dfferent folders? Maybe the wrong one is getting updated.

Failing that, are you using any commercial framework? Is it possible that if you return to form A but don't explicitly call some sort of .Save() method, those values may be automagically reverted for you?

What is different between the dev and production environments? Are they on the same computer? What network, if any? Antivirus (server and workstation)? Any other system-level utilities in play? Same VFP9 SP level on dev and production? Workstation OS(s)?