Error after converting to MS Access 2003

[LynnEsther]

Hello. We converted an access 2000 database to 2003 and are getting the following error when opening some forms:

"The expression On Open you entered as the event property setting produced the following error: Member already exists in an object module from which this object module derives."

This error is baffeling me. There is no "debug" option on the error message. My On Open event only had two lines of code and so I deleted the event to see what happens. Now, I get the error on the next event (On Current) and so on an so forth. Does anyone know what this is or how to correct it?

Thanks very, very much in advance.

 

[dkinley]

Sounds like a module has the same name as a function within the module. Or a control within the form has the same name of a sub or function/module.

I would assume that the form in question is calling this function and the program is either getting confused with the module and/or the control on the form.

If that is not it - then I have no idea without taking it apart.

-dK

 

[LynnEsther]

Not sure that is it, although I will look at it. The odd thing is that these forms worked perfectly in Access 2000. That's why I'm wondering if the problem is some Access 2003-centric thing. Any thoughts out there?

 

[Rabbie]

ADO was the default in A2000. I think that DAO is the default in A2003. Make sure that references in any VBA code are made unambiguous by specifally declaring recordsets etc with their correct type.

 

[LynnEsther]

Well, news to me. It turned out to be similar to the first reply. I had several forms that had a subroutine that I named DataChange. A2003 apparently did not like the same named subroutine in multiple forms. I gave each a unique name and the problem is now gone. I think a better solution is to create one module and then have the other forms call that one module. I will do that next. Thanks for all your replies.

 

[dkinley]

No problem. Glad it was something simple and not too wierd.

-dK