I don't know if anyone has any ideas about this strange issue I have come across.
A program (which I did not write and have no access to code) has a maintenance form for monthly budgets.
The table it uses has 12 fields nb01 to nb12 (one for each month).
They have used an import program (which again is out of my control) to import a load of budgets.
Looking at the table, all the figures have been imported. However when using the maintenance form, the budget for month 3 (field nb03) always shows zero.
As there are definitely figures for month 3, I assumed that this is some bug in the form (which if you remember I don't have the code for).
However, if you use the form to enter the figure for month 3, all is well. It will display it correctly.
From browsing the table, nothing has changed! The data is the same.
I have tried re-entering the figures when browsing the table, and using the replace command from within a program to re-enter these month 3 figures, but neither method works. It only shows the month 3 figure correctly if you use the maintenance form.
e.g. After importing the records, a record of the table shows
account = "Test"
nb01 = 15
nb02 = 12
nb03 = 10
nb04 = 16
...
nb12 = 18
Doing a "? nb03" in the command window returns the correct value (10) for that record.
If we now run the program and go into the maintenance form it shows (for that record)
Account Test
month 1 15
month 2 12
month 3 0
month 4 16
...
month 12 18
If I edit month 3 with the value 10 then it will display that figure from then on. However the data in the table record has not changed (at least not visually).
(I can confirm from testing that the form ONLY writes to that one table and ONLY updates the fields nb01 to nb12. The 12 month fields are all numeric size 9).
Is this behaviour familiar to anyone? Or am I condemned to enter lots of month 3 figures one at a time manually :(
UPDATE
I created a copy of the table, imported the data from the original and then inserted my new table in place of the old table in the database. Now all works fine!! I'm guessing some weird corruption in the table was causing this problem.