You can use your favorite social network to register or link an existing account:
Or use your email address to register without a social network:
Sign in with these social networks:
Or enter your username and password
Forgot your password?
Yes, please link my existing account with for quick, secure access.
No, I would like to create a new account with my profile information.
A customer's post on TechNet brought one of my colleague's attention to an error folks are seeing after applying SP1 to 64-bit Access installations and then trying to use a wizard:
The database cannot be opened because the VBA project contained in it cannot be read. ... To open the database and delete the VBA project without creating a backup copy, click OK.
On clicking OK, Access doesn't open the database, offering this error message:
The code contains a syntax error, or a <DB_NAME> function you need is not available. If the syntax is correct, check the Control Wizards subkey or the Libraries key in the <DB_NAME> section of the windows registry to verify that the entries you need are listed and available.
Apparently, the VBE7.DLL file update included in the service pack prevents the opening of .ACCDE files compiled using RTM 64-bit Access. Because wizards are .ACCDE files, they could trigger the error depending on when they were compiled.
The customer who posted reports that uninstalling the service pack restores the functionality, and advises that people with 64-bit Access wait until a solution is provided before applying SP1. TechNet agrees (the mod marked it as an Answer), and so do I.
Stay tuned for that solution...
UPDATE: My colleagues are working hard to fix the problem with 64-bit SP1. Meanwhile, we've got a fairly simple workaround - 1) Delete all files in the <%Program Files%>\Microsoft Office\Office 14\ACCWIZ\ folder, 2) Boot Access - Setup will restore the missing wizard files.
Just FYI, I have Access 2010 x64 with SP1 on one of my test machines, but have not encountered this problem. The wizards are working correctly.
I upgraded from the private beta of SP1 though, so maybe that made a difference.
Very disappointing that this happened. What a mess. This happened with the Access 2007 SP1 too.
I wanted to confirm that we at FMS have received reports of this problem from customers of our Access 2010 64 bit products. We have reproduced it internally, and are working on solution(s) to address this for our products. On the plus side, we have not seen problems with ACCDE files created with the 32 bit version.
Also in Access 32-bit there is an error.
It is assumed that it does is fix some bugs in version 2010 without question this correction, in practice all the changes you make to the database open and modified from the installation of Office 2010 SP1 .. . all the bases ended up as corrupt.
What happened? or rather, what happened to me? because when I worked in a database format in Access 2010 SP1 2010, while the base was left open to make all the changes and everything worked operationally, but when these two things came to the error:
1. When the base was open, make changes to forms, new controls and VBA code running ALT + F11 to compile ... or similar message appeared: "Access has stopped working ..." and created a backup database also corrupt.
2. When modifying forms, creating new controls and suddenly gave clicking one button (before and it worked correctly, being an old form) will automatically close the database file being aired on "alccdb" and trying to open the base again and again the error message appeared: "Access has stopped working ..." and created another equally corrupt backup.
I also have seen some lockups in Access 32 after sp1.
However, my solution was to do a de-compile. Once a de-compile has been done, my freeze ups have all disappeared, and stability is again rock solid.
So, perhaps some attempt a de-compile to see if this helps, it certainly did the trick for me.
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
Any connection with social.msdn.microsoft.com/.../3a4ce946-effa-4f77-98a6-34f11c6b5a13
However, when Desistale 32-bit SP1, Access 2010 and does not identify all the bases as currupt (including backups Access) and now if I can compile. Not that the 32-bit SP1 has a bug?
Anyway I'll try what you mention has de-compile to see such. The downside is that it was almost eleven different projects of Access, with all the work that I have over past due because of SP1, to walk now playing with SP1.
Thanks for all the comments!
Vladimir, I'm not aware of any connection between this issue and any Windows service packs but I can make that part of my follow-up.
Sorry to hijack this thread, but can someone please tell us when Office365 is going to support reporting with Access web databases? I've asked on a couple of the forums, but no-one seems to know anything. Office365 has been out of beta for a while, yet this fairly central functionality (for Access 2010 users) is not operational with no news of even whether it will be made operational, let alone when. Should I ditch the whole thing and find another provider? Thanks.
No worries Alan - but I don't know any more about it than you do. I agree that reporting is a central part of Access - especially an Access 2010 web database. I'll share as much information as I can here in a future post about Office 365, but your best bet is to keep at the Office365 community - I know they are working hard to deliver, and you'll hear from them as soon as they have a solution in sight.
Access 2010 SP1 on 32bit prevents runtime from from running accde files resulting in the message "The database cannot be opened because the VBA project contained in it cannot be read. ... To open the database and delete the VBA project without creating a backup copy, click OK." Uninstalling SP1 cured the problem.
Also, ADODB connection now fails in the accde file in runtime.
Can anyone help please.
ADODB bug: social.msdn.microsoft.com/.../3a4ce946-effa-4f77-98a6-34f11c6b5a13
We have confirmed this impacts the 64-bit versions of our Access 2010 versions of Total Access Emailer (www.fmsinc.com/.../Email.asp) and Total Access Statistics (www.fmsinc.com/.../StatisticalAnalysis.html). Free updates of these will be provided for existing customers as soon as it goes through our QA process. There is no change needed for the 32 bit versions.
said: "There is no change needed for the 32 bit versions."
Access as a finished product "accde" no problems, but as a product in development "accdb" if there are problems in the 32-bit with SP1 Access.
Glad to hear your 64-bit utilities are on the mend, Luke!
Folks, the team is still looking into the issue with 32-bit systems. As soon as I have any confirmed details, I'll post about it separately.
I really appreciate all your feedback - I must say this is a solid community. Thanks for making this blog work!
'There is no change needed for the 32 bit versions'
Actually I'm running 32 bit on XP. After installing SP1 all my previous ACCDB's seemed ok until I made a change to code, then after compiling, closing and trying to reopen the db's crash. I've also seen numerous other comments with the very same problme. So 32Bit IS an issue.
What's happened to the guys at MS rolling out a SP without testing it properly. I've wasted days on this. Thought I had it cracked after repairing Office installation but today I'm back with the same problem. If I'd have done this to my customers I'd loose them in flash.