Search results

Thanks for the reply. The file which we use Access 2003 for is on a shared drive - however it's a red herring, as even creating a blank MDB on the user's local PC, with nothing in it but a form with a button that fires a MsgBox will cause the error I have reinstalled Access, but I believe it...

Good question, hadn't thought about the 32/64 bit thing, although as far as I remember I don't think it even lets you install mismatching versions It's possible they could be mistakenly trying to open it in A2016 first and then opening it up in 2003 (as I know one of these users does use 2016...

I don't get any warnings whilst installing, no, everything appears to install correctly. List of references is the same as yours and also the same as my own machine which works correctly (and also has both Office 2003 and 2016) Really frustrating one :( I've just noticed that the affected...

I agree it sounds like a references issue, however what's strange in this instance is that there are no references missing, and they are using the correct version for 2003 (Access 11.0 Object Library). Repair doesn't seem to be having any effect either

Hi, wondering if anyone can offer any help on why this error message is triggered by trying to run any VBA code with Access 2003 running on Windows 10: This has started happening in the last few weeks with two users at my company. It doesn't appear linked to a particular database file - I can...

I have to agree with all the above. I've taken a look at the information on the "What's New fo Access 2013" page and don't like what I see at all. I'd hardly describe myself as some luddite clinging to old technology, but I've got a sprawling ADP which has developed over the last 6½ years and...