-
OK, in addition to my earlier query it's now becoming clearer that there is something seriously wrong. I've just had an example where a user had opened a form, searched for a record, found the record, then changed one field ( which has NO code attached to anything ), then whenever they click into a different field the data contained within it changes to that of a different record!, this then happens for all the fields on the form, this is on a form that's been working fine for months, the .mdb data store is fine, it Jetcomp's fine, anybody got any ideas at all?, anything even very small would be appreciated.
-
-
It's DAO, but there's no code behind the form, it's just a bog standard Access form onto a table, how can it be changing?
Thanks for the reply
-
Can you send me an example of the code (to the .centrica address) };-P
------------------
Matt G
Either [email protected]] or [email protected]
-
Thanks again for the reply. I appreciate your offer to look at the code but there really isn't anything behind it. Let me elaborate......
Imagine you set up a table in access, anything, maybe just Title, Forename, Surname and Date of Birth.
Now imagine that you link that table into another access database that you intend to run purely as the front end. You create a form based on the table with no code behind it at all.
Using record selectors / search criteria whatever standard way of finding a record you want ( those available through the Access wizards for example ), you find the record you are interested in.
You then click in the D.O.B. field to change the date of birth, which you do, you then click in the surname field which magically changes to another surname pulled seemingly at random from somewhere else in the table. Then if you click on the forename, the same thing happens. Remember that there is no code behind the date of birth field, how is this possible?.
I'm not kidding, I know this sounds ridiculous without some sort of update / sort / find event being triggered from somewhere, but it is happening.
Granted that the form is more complicated than the simple example above, but it's exactly the same principle... that's why I was wondering whether anybody might know of any problems created by network speed / update latency etc.
This problem has occured running 97 front end 97 back end, but now, to add a complication, it's an Access 2000 front end, running on a 97 dataset, why?, because we've been told this will be fine by MS, and we also can't find a version of jetcomp to run on 2000 data sets ( i.e. if the back end corrupts and Access 2000 can't open it I'm stuffed ). If anyone knows of any problems running this configuration please enlighten me.
Thanks again for the help so far.... please keep it coming....
