Access 2003 crashing on Windows 7

[trevorwilliams2]

We have just purchased a number of new computers loaded with Windows 7 Pro.

With Office 2003 installed and all of the latest patches I am suddenly running into problems with Access crashing when it opens.

My main menu loads, then maximizes, and the second you click on any control, Access crashes. No error code just the "We're sorry for the inconvenience but Microsoft Access has encountered an error and has to close....”

This is common to the 4 PC's with 7 on them.

I have not had much luck finding an answer for this.

Is anybody else running into this?

 

[kjv1611]

Have you seen this?

http://answers.microsoft.com/en-us/...indows-7/0d0827a6-8acc-4365-b3bc-945ddd0de760

You can find more like it here, if not.

Otherwise, what have you tried?

 

[genomon]

Not having an available printer installed as default will cause this.

Gluais faicilleach le cupan làn

 

[trevorwilliams2]

Default printers are installed & I'm using the office 11 object library.
The database opens fine when just going to the database window (shift) so I know that it has to do my main menu.

The main menu has some positioning of buttons etc. in the resize event. I suspect that this is what is irritating the DB.

Trying to get time on the offending machines has made this dfficult to debug.

 

[kjv1611]

Have you tried stepping through the code during startup? That might help narrow down the specific offending line(s). Easiest way to do that for a startup item is this:
[ol][li]In the VB Editor, find the OnLoad event, or whatever event you are using to trigger everything at startup.[/li]
[li]Place a break mark on a line that runs during startup, preferably early on in the process to be sure you catch the bad step(s). (To do so, simply left click just to the left of the line where you want to put the break mark. It'll add a dark red circle at the beginning of that line, and place dark red "highlighting" around the text.[/li]
[li]Save the database via the vb Editor's File-Save.[/li]
[li]Close and reopen the database[/li]
[li]Step through the code, using <F8>[/li][/ol]

 

[MajP]

Prior to checking the code you may want to see if the form itself is offending. Copy the form and remove the code. Then remove the class module by setting "hasModule" to false. See if this opens without any code.

 

[BallunarCrew]

Was this ever resolved? I am having similar issues with a PC with Windows 7 but the database is in Access 2007. When I load the main form, which is very complex, it tells me, several times, "No object in this control". Once I get through all the messages, it seems to run fine. This is only occuring on the machine with Windows 7 on it. The others are runing XP. I also get these messages quite often: The expression On Get Focus you entered as the event property setting produced the following error: Object or class does not support the set of events. The expression On Current you entered as the event property setting produced the following error: Object or class does not support the set of events.

 

[kjv1611]

BallunarCrew,

This is not the same issue for sure. You need to start your own thread. Access Crashing vs giving error messages is totally different.

 

[trevorwilliams2]

Just to follow up my thread here.
Just got done upgrading to Access 2010. Problem solved.

 

[kjv1611]

Glad to hear your problem is resolved, trevor.

"But thanks be to God, which giveth us the victory through our Lord Jesus Christ." 1 Corinthians 15:57