Bulid event crash

HDEvKev

Registered User.
Local time
Today, 00:23
Joined
May 9, 2013
Messages
18
I am trying to build an event when I double click a field. As soon as I click on Code Builder, access crashes. It does this with every access database I open.
 
Hmm, try importing all Object into a clean database and seeing if the same thing happens.
 
Could this be a reference problem or an ActiveX control issue! I vaguely remember a similar issue with one ActiveX control in Access 2010.
 
@vbaInet

Do you mean the Calendar Control if the database has been upgraded from an earlier version? Nothing else comes to mind...

If that's it then when the OP imports the Objects into the new database the problem will still be there. However, I always do this first as sometimes the Project becomes corrupt when folks forget to Compile their code and exit the database. Usually, you can clean that up with an import into a clean Container.
 
@GinaWhipp: Erm, I think it was the image list control.
 
@vbaInet

Hmm, never ran across that but then I don't know everything! :eek:
 
The plot thickens. My problem is limited to my laptop. Have no problem opening the code builder on the other machines on the network. I have both Office 2007 and 2010 running on my laptop. All the office programs are running the 2010 version except Access. If I open the DB in 2010, I have no problems with the Code Builder.
 
I made it to the references window and then I got lost. The article didn't really explain what to do once I got there. I don't have a lot knowledge or experience coding so you'll have to excuse me.
 
You needed to look at all the checked ones at the top and see if any say MISSING. If they do uncheck. Ignore the ones that are unchecked.
 
Oops, forgot, at the bottom check to make sure none of the ones indicated are checked. If they are uncheck those as well.
 
I think the two versions of Access are causing conflicts, perhaps the wizard libraries. I may have had the same problem running Access 2003 and 2007 on the same machine and I resorted to running it on a virtual machine.

You might need to re-install Access 2007 or forgo one version of Access.
 
I Think you're right vbaInet. I kept using the 2007 ver. because at the time, I had some computers still running XP with 2003. Now that I have everybody on Windows 7 and Office 2010 or 2013 maybe I should take the leap to 2013.
 
Since you're application is on 2010 I'll stay stick to 2010. If you want to pickup 2013 install on your VM or on another machine.
 
In addition... can you please post the References you have checked here? Want to make sure there are no conflicts.
 
I misspoke when I said I was running 2007 and 2010 on my machine. I'm running 2007 and 2013, as are 2 other machines. I also have 4 machines running 2010, but I do all the programming on my machine.
 
One, you should be using the lowest version to develop in. Two, please post your References, only the ones that are checked.
 

Users who are viewing this thread

Back
Top Bottom