Record missing after restarting program

Maybe in a cleanup somewhere there is a DELETE command without specifying the right ALIAS and since that table is the current one in use, its last record gets deleted.

Have you used the TRACE window to examine your code in operation line-by-line?

If you do so you will know what is going on.

Either use Breakpoints at critical points or use SET STEP ON to 'break' execution while in Development mode and then follow the code's execution.

Good Luck

Also check the codes in your Forms' Activate and Deactivate Methods.

You could answer another questions which could help to investigate what is happening:

If you enter new order and exit the form are all lines saved?
If you add lines to existing order and then you enter new order are all lines saved?
If you just change quantity in existing line is it saved?
Do you check order lines existence in database from the same computer as they are created?
Are missing records deleted physically or just marked for deletion?
Is it possible to execute your application from VFP under the Debug window? If yes, you should try breakpoints on RECCOUNT() and DELETED() in appropriate workarea and record.

To be honest, the missing TABLEUPDATE() seems to me as the most probably reason for app behaviour (in Order edit part).

I second pcelba. Especially if you check your DBF from the same computer you change the order, all you might see is buffered changes not yet committed to the DBF file. So only if you check the same DBF from another PC you'd see if the changes are saved.

Bye, Olaf.

To answer a couple of the questions from pcelba:
1.Entering a new order, all lines are saved. Close program completely and restart, new order is there and complete.
2. Add lines to existing order then add all new order. New Order saved correctly, lines added to existing order gone as usual.
3. Change quantity in existing line.  Hmm. does not save it. reverts back to original number.
4. I am checking the existence in the database on the same computer as it is created.
5. Once i restart the program, if I physically look at the table, the new lines are gone completely.

I do have a tableupdate() command on exist from the form. That's why this has me a bit baffled. I haven't had the time to work with the debug window on this. Will try again to get to it today. As I mentioned earlier, what is strange to me is that all looks good with the program. You can go to other functions, print reports, whatever, and the added/editing lines appear as they should. But as soon as you exist the program and restart the program, those changes are gone.

But it really seems to missing TABLEUPDATE() or error in its call. Do you check the return value from TABLEUPDATE()? Could you check if it is really executed?

It's been a while since I had an opportunity to work on this problem. It still exists and I really need to get it corrected in order to successfully implement the program. In further testing i have figured out that the records in the grid on the form are the ones that are disappearing. Any other field that i change is saved correctly. It has to be something in the grid.

Is the grid based on a buffered view, which in turn is based on a buffered table. I think you need 2 tableupdates then.

If you know where is the code used to save grid data then you should place SET STEP ON to this code and look what is hapenning. If you don't know the right place then you have to trace almost every method used during the save operation.