Question Access 2010 Control Wizard

[ted.martin]

Last week our pc people did a clean install of Windows 7 Pro and Office 2010 from previously Vista Pro and Office 2007.

I have now noticed a problem with Access 2010 and the Control Wizard. When creating a new form and (say) adding a button, when the wizard runs I usually select cancel and then write code behind the button rather than use the embedded macro.

When closing the database and then opening the form and pressing the button, I immediately get an "Access Not Working" message followed by "Windows is trying to find a solution" (which it doesn't). I am fairly certain that the form/button is corrupting the programme.

I have now turned off the wizard and (hopefully) the problem has gone away - time will tell.

Either way, I am convinced its this Wizard that is causing the problem and my questioning mind says WHY because with Access 2007, it was never a problem and sometimes it was useful - like inserting subforms.

If anyone has any thoughts on this or even a 'fix' then please let me know.

Thank you

 

[GinaWhipp]

Have you tried to run the Repair? I would also disable any Anti-Virus you are running while doing so.

 

[ted.martin]

Have tried repair but with av running; to no effect. Why did you suggest disabling the av?. Thanks for your response, appreciate

 

[GinaWhipp]

Because I have often found that when installing software the AV silently kills parts it thinks are dangerous. So, I will ALWAYS disable my AV when installing software.

 

[ted.martin]

Thanks for that. Office 2010 was installed before the Trend Micro AV was added so I guess Repair is not the solution.

Just tested it again and it is definitely the Control Wizard that is causing a problem. Did a simple button on a form, cancelled the wizard when it ran, and put simple Docmd.close acform, "Form1" behind the button. Closed the db, opened Form1 and pressed the button and the same "Access not working message came up. Did the same thing again but with the Wizard Control off and it worked fine.

Hey ho - looks like the upgrade does not like the wizard.

 

[GinaWhipp]

Oh, I was suggesting you turn of the AV prior to running the Repair, once the Repair is run turn the AV back on and see what happens. Also, you database is in a Trusted Location right?

I am not saying the wizardis not bad (or corrupt), I am just trying to get it working again.

 

[ted.martin]

Yes - trusted location is fine. Anyway - doing as you suggest and will get back to you. I appreciate your help. There is clearly something odd going on and I am determined to get to the bottom of it.

Will respond soon. Please bear with me. T

 

[ted.martin]

I wish I could say that has fixed it but it has not. Unfortunately I am now in real trouble as despite what I said about the Control Wizard, after doing 2 hours of coding that seemed OK, the db now has the same problem with any button I press. I can only think that the install was somehow faulty.

It will be Monday before i can get our techies to look at this but as you will appreciate it is incredibly frustrating.

Trying to smile but it is difficult.

If I eMail the app to you; could you see if you can open it? Test it by pressing the switchboard close button; that is where it crashes now.

Thanks

 

[GinaWhipp]

Okay, testing now...

 

[GinaWhipp]

Okay, it wouldn't even open for me so I have created a new database and am importing all the objects into it. So far I have gotten the tables and queries and then everything stops. This database is corrupted... That whole wizard thing must have been a warning... I'll keep you posted if I find anything!

 

[GinaWhipp]

Okay, I finally got it to open but then anything else tried results in crashing. It is not Access that is the problem but the database. PLEASE say you have a back-up?

 

[ted.martin]

I do have a backup but about 2 hours ago so its not the end of the world. What I am designing is not complex and I have just repeated the past 2 hours on my own personal pc (not work laptop) albeit in Access 2007 without a problem.

Thank you for trying to open it. So the big Q now is what is causing Access 2010 to crash? I do not believe its my code. It has to be something else.

I am tired now; its 23;50 and at least I can sleep easier having recovered my work but apart from chucking that upgrade in the bin, not sure what else to do.

Night night.

 

[GinaWhipp]

Get some rest, we have time... In the meantime, going to try opeining in Access 2007 and seeing what happens.

 

[GinaWhipp]

Oksy, I found the problem and its not corruption (glad you mentioned Access 2007)... Remove the Reference to...

Microsoft Office 12.0 Object Library

...and any other 12.0 Object Library which does break your Modules BUT those were not written with Access 2010 in mind. You will need to find another way to do those functions, sorry... I did not try to see if those Modules will work with the Reference to the 14.0 libraries, they may very work fine. I was just glad to make it stop crashing in Access 2010.

I'm a happer camper!

 

[ted.martin]

Good morning from the UK; well what you said makes sense but looking at some of the archive backups they are all using 14 Library. Did you manage to get my file open and that's how you discovered the 12? If so how did you do this as although I can open the faulty db, I can't get to the modules code to look at the references in v2010?


In other words - what did you find and how?

I appreciate your time on this. I have a 2007 version thats running and almost back to where the faulty one was in design terms.

I look forward to hearing from you. T

 

[ted.martin]

Further thoughts: I have got the faulty db open in 2007 and of course changed the references back to Lib12. Success in terms of recovery.

Put this same one back onto v2010 and all the References automatically reverted to lib14 and Success in opening it and running it in 2010.

Just looked at some of my other db's that were brought forward from v2007 and all of them have automatically gone to v14 Lib (as you would expect), including the famous 2 hour ago Back-Up.

Are you saying that the faulty db I sent you had a mix of v12 and 14 Libraries? If that is so, then that would surprise me.

One thing I did do during the design of the faulty 2010, which may help the "evidence trail" was import a very simple table from a previous db designed in v2007 into the v2010. Do you think that this could be the root of the problem?

 

[stopher]

I'm guessing Gina is sleeping just now so I'll try and help.

You can open the database without running any code by holding down the shift key then clicking on the database to open it. Make sure you keep the shift key held down throughout until you are sure the database is fully open.

Then you should be able to navigate to the VBA editor (or press ctrl-G to open the editor)

hth
Chris

Edit: Sorry, I didn't see your latest post.

 

[ted.martin]

Thats OK Stopher - thats how I did it. Hope Gina sleeps well, she will no doubt respond this afternoon.

BTW - quite remarkable how close the coding was between the original and last night's re-write.

 

[ted.martin]

Hi Gina - can you try this for me, please in Access 2010.

Open the attached and in Design view, make sure the Control Wizard in On and then add a button to the form F-Quotations. When the wizard starts, press Cancel. Then using the On Click event ellipsis, add this line of code

  Docmd.Openform "AF-Administrative Tools

Close the database and re-open.
Chose Quotations Summary (if you get that far!)
Double-Click the Quotation No. of any and then try pressing the new button when the form opens.

Even though all the Libraries are 14, this "Access has stopped working " comes up straight away on my pc.

This is exactly the problem I have been writing about and it would be interesting to rule out whether its my LapTop or something more fundamental.

Much appreciated. Thanks

 

[GinaWhipp]

Good morning from the US!

Once you said you could open in Access 2007 (HELLO, why didn't I try that!) I was then able to open it. I first looked at the Modules and noticed quite a few said, in the Declarations part, that 12.0 Object Library required. So I went and checked References and saw *early binding* so, I unchecked ANY Reference that said 12.0, including the Word one and closed the database.

I then reopened in Access 2010 and went to check the References and they all did what they were suppose to do, which is change to 14.0. I then said okay let's be sure that was the problem. I opened the back-up one I have saved in its original state and yep the problem showed it's ugly head. So, I started unchecking References and reopening until again all had done what they were suppose to do which is change to 14.0

Having confirmed it was the References I went and really *read* the Modules. Again I saw that they *required* those 12.0 Libraries get checked. So, now that they had all switched I ran Debug > Compile from with a Module telling it to Compile the entire Project (database) and low and behold quite a few returned errors to they definitelt wnat the 12.0 Libraries. That is how I determined those Modules either need to be updated and/or changed out depending n where you are using them.

When using Modules, if they require *early binding*, which yours do, then those are not the ones you want to use if you plan to span the use of your database over different versions. You need to look for *late binding* ones that way no matter what the version of Access your Modules won't fail. For a better explanation of Early Binding vs. Late Binding see...

http://www.granite.ab.ca/access/latebinding.htm

Hope I explained that clear enough...