Big problem - ""ME."" doesn't work anymore!!

[Shiner83]

Hello, I have a big problem with my access project, and it couldn't happen at a worse time. I've been working on my project for 2 months, and it's been working fine and I was supposed to finish today. BUT... I had the horrible surprise to realize this morning that my project didn't work at all this morning! As soon as I opened a Form, Access crashed. It turns out that the "me." statement is the source of the problem. For example, a simple command like:

Me.CmdOk.Visible = True

provoke the crash. Every form does it. When I change Me. for "Forms![Name_Of_Form]." it works correctly. But I have a lot of time where I utilize CmdOk.visible instead of Me.Cmdok.visible, and these are hard to find manually. Also my report system works on the basis that I can create new one and they will work because of the Me. I use, if I have to create new one using the Reports![Name of Report]. I won't be able to create new tables. Plus, there's of course the additional problem that I can't see yet and i'm afraid there could be more...

So, ANY kind of help would be appreciated. I need to find an answer, fast, to solve this problem before leaving :S...

 

[Chance1234]

1. Try compact and repair the database

2. Try open the database using a command line with the switch /decompile

3. Go into any vba module look at references, see if there is any question marks. if so untick the ones which have the questions mark or error, come out of access reopen and then re-reference them

4. as above go in to a vba module , add in a couple of other references , come out , go back in and then remove those references.



Chance,

Filmmaker, gentlemen and Cavalier

http://WWW.5YLAC.S5.COM

,

http://WWW.HOWTOBESPOOKY.CO.UK,

http://WWW.HENRYV.CO.UK

 

[Shiner83]

I think I found the culprit. The references, and Access 2000! Yesterday I opened my database on the network with Access 2000, instead of the Access 2003 I used to create it. You were right about the reference, I went there, and even if they seemed correct, I modified them a bit and now my database works again.

What a relief

Now however is there anyway to avoid this problem in the future? I won't be working here in the future and I don't think they will think about checking references if they have the same problem. Is there any automatic way in Access to set references? If not, I guess the best I could do is create a paper copy of the instructions they need to do in case of problem?

BTW, here's the refences I use with Access 2003:

Visual Basic for Applications
Microsoft Access 11.0 Object Library
Microsoft DAO 3.6 Object Library
Microsoft ActiveX Data Objects 2.1 Library
Microsoft Excel 10.0 Object Library
OLE Automation
IAS helper COM Component 1.0 Type Library

What should I change to make it work in Access 2000? I'm thinking I might make 2 copies of the database, one for 2000 and the other for 2003...

 

[Chance1234]

To be honest, i have been working with Access for well over 7 years, I have only ever had the above problem once so i wouldnt fret to much about it.

however what might be wroth doing is any procedure u have that relies on a reference jsut add in a comment line stating what it is.

ie.

'---------REF: Microsoft DAO 3.6,OLE Automation

Chance,

Filmmaker, gentlemen and Cavalier

http://WWW.5YLAC.S5.COM

,

http://WWW.HOWTOBESPOOKY.CO.UK,

http://WWW.HENRYV.CO.UK