BEFUDDLED & BEWILDERED

[aldeb]

Everyone,

I have a database created with Office 2000. I have a form with this database. I tested this database with Office 2003 and it works just fine. My dilemma is as follows.

Since my computer was upgraded with Office 2003 I am having the following problem. If I take this form to Design View and then back to Form View I do not have a problem. If when I take the Form to Design View and then I go to the VBA Code Module (I do not change a thing) then go back to Form View I have problems. It will create a backup of the database. I get "Run-time Error '434' Object doesn't support this property or method. Again, I have not changed a thing. This only happens if I have switched to the VBA Code Module. Again, all I have to do is open the VBA Code Module and close it down without changing anything and I have this problem. It seems somehow that opening the VBA Code Module where the problem is.

Please help, this is driving me crazy!!!

 

[mohammadagul]

Go to you vba.
compile the database
check the references
i believe the problem should be with some reference for some active x control you are using in your forms.

 

[aldeb]

Well here is the latest that I have discovered on this problem.

If I copy my database to an Office2000 computer I can make all of the code changes I need and then copy the database back onto a office 2003 computer and everthing works fine. I just cannot change any code on the office 2003 computer. Anymore ideas out there???

 

[godofhell]

Access 2003 changed some of the code references on the controls, you might have a control that Access 2003 sees as not having a valid property. When it crashes on you, does it give you the option to Debug it? If it does, debug it and see what control it is referencing and change it. The other things that might be causing this problem is that in your Access 2000 you are set not to have to declare all the variables you create and in Access2003 you are set to decleare all variables. My personal feeling is that you have a control refered to in code that access 2003 sees as having an invalid property set.

 

[Raneil]

Check your JET.

Hi,

You may want to read the following article: http://support.microsoft.com/default.aspx?scid=kb;en-us;294698

This article discusses the security feature incorporated in Jet 4.0 which prevents (usually silently) some functions and expressions from executing. It's a pain in the butt because you might have to go thru all your codes, identify all the functions that are no longer allowed in Access 2003 using the high or medium security feature. I set my security feature to "Low" and my codes still blow up. The best solution would be to go back to the previous version of Office, but my workplace has already migrated to Office 2003, which in my opinion doesn't really give us any advantage. But anyway, read the article, it might give you an idea why you are having your problems.

Hope this helps.

Raneil