Access Update Problems

I'm having some very strange problems with a couple of access databases I run. My users open a form, just like any other in Access, which is bound to a linked table, they then open another form on top of that, it doesn't matter what the form does, and the form is in now way connected or related to the recordset of the first. When they close this new form SOMETIMES they find that the record they were looking at has changed, the details of another record are now displayed, but NOTHING has occured in code or otherwise to alter the displayed record. This is an intermittant problem, the form used has a very large number of fields, we can find nothing to give us a clue to what's causing it. I've compacted, repaired, and completely re-imported all the tables from one access database to another, upgraded into 2000, nothing seems to work. Has anyone else every experienced anything like this?, could it be related to network performance?, I've increased the timeout and refresh settings. Any suggestions, no matter how small or seemingly obvious would be greatly appreciated. Thanks

Hi Jottiwell,

I have a couple of ideas, (neither may pan out, but it's worth mentioning...)

1) Are you in some way reloading the table when you come back into that first form (ie have the table reload in a form load or form initialize event)

2) if you call back and forth between the forms, you may be triggering a reload of the table....

3) if you are using ADO controls with Data combo boxes, events get triggered behind the scenes... this may be causing a problem...


I recommend stepping through line by line...
Sometimes with form interactivity errors, the timing of the debugger fixes small problems, so if you step through and dont find anything, use message boxes in strategically located areas.

Hope this helps!

~Sam

Thanks for the reply,

I appreciate what you're suggesting, if Access is triggering a form reload wouldn't the problem show itself up all the time?. What I mean is that when I come back to the original form wouldn't the change happen every time?. At the moment the problem is intermittent and I can find no common factor to link it's occurances. Any ideas relating the network performance / recordset update latency?

Again thanks and any other suggestions would be appreciated