Search results for query: *

Sorry where it says DoCmd.RunCommand it should say DoCmd.RunCommand acCmdSelectRecord Oops :)

Try; DoCmd.SetWarnings False DoCmd.RunCommand DoCmd.RunCommand acCmdSpelling DoCmd.SetWarnings True That's what's written on other tek tips posts, and it seems to work in my databases.

Further to everyone else's answers, it may be useful to include the code at http://www.mvps.org/access/api/api0041.htm when your database loads. It means that any additional copies of the database will be closed once they see there is already a copy open. Mail merges appear to work fine anyway...

Thanks for your help OnTheFly, it turns out the issue was due to the user not having a certain Outlook reference installed - we sent them an shift unlocked database and they disabled the reference (they weren't using Outlook functionality of the system anyway). That was curious behaviour as...

Thanks for your help. It may be an issue with recordsets, but another client is running the same database on Access 2000 without any major problems - the only issue encountered was that a couple of the references needed changing. As far as I'm aware the database doesn't load up using the shift...

Hello, I wondered if anyone could help with an issue I'm having with a database. The database was developed in Access 97, but one client has Access 2000 installed on their machine. We converted the database using Access 2000 and sent it to them but when they try to load it Access 2000 just sits...

I had this problem too. Check out http://www.mvps.org/access/bugs/bugs0011.htm