Has anyone seen an instance where a user makes a change to a new record (via a form) and the field changes are committed to the index but not the table?
I have a weird issue where this is happening. If you browse the table via the index tag, there is a blank record in the correct location for the field value that was entered!
Here's an example:
There are existing records in a table for Test1,Test2,Test3,Test5
My user enters a new record called Test4
Browsing the table, the last record (the new one) is blank, however, if you set order of the table via the index tag the blank record shows up after Test3 and before Test5 meaning that somehow the index is committed even though the table changes are discarded.
Not using table/record buffering of any kind.... editing the tables directly.
I'm wondering if this isn't another bug/quirk with VFP9SP2 related to using the same table AGAIN with alias as I have some validate code in the form that opens the table again alias.
Brandon Harker
Sebae Data Solutions