Network drive Access bombing on fixed errors

[SBendBuckeye]

I am putting together an Access97 project for a user which is stored on a network drive. Before lunch I fixed an error caused by forgetting to mark Parm2 as optional.

My user called me after lunch saying she was getting a required parm error at the same spot. Accessing it from my area worked fine. I had her completely exit out of Access and come back in and the problem still persisted.

I wish I would have had her logoff and logon again to see if that fixed the problem. It almost seems like Access was never flushed out of memory and was running an old version already loaded.

The application is not yet flagged for multiuser use if that makes a difference. Have others encountered this situation?

Thanks and have a great day!

 

[930driver]

I saw this behavior a few years ago with an A97 mdb. As you say, it would correct it's self by restarting Access. I don't know why it's not working for you, might try the old reboot.

On a related aside, I hope you are planning on splitting your mdb into front end/ back end, else you are likely to continue having problems. "The Key, The Whole Key, and Nothing But The Key, So Help Me Codd!"