Access 2010 accde error

Question

I created an .accde file of my split database. The data is on a server in a shared folder with system wide permissions. The FE is what I want to create the accde of to limit users being able to modify desgin.  Every time I try to create the file, it's created without any errors or issues.  But, upon opening it up on the same computer or any other computer (win7 & XP machines) I get this error:   the database cannot be opened because the vba project contained in it cannot be read the database

This database has a few simple macros, nothing complex and all from built in "stock" code. 

I've read that sometimes this happens when working on 64 bit and 32 bit machines and something about service pack 1.  Well, all our machines are 32 bit and it's a group licensing from Microsoft, so there's absolutely no difference between one client machine and another as far as Access is concerned.  Except for some being win7 and others XP, but all are 32 bit.

I even tried to make an accde file from a fresh database with 3 tables, no data, no macros, no VBA and guess what... same error.  The error even says something about vba and on that attempt, there was never any to begin with.

How can I get past this issue?

Thanks

Adam

Answer 1

Hi Tom,

Sorry, I didn’t see the article listed in your post, my fault.  I understand an ACCDE file compiles the application, but I have also seen this similar behavior with a few different customers now and we were able to get around the problem by manually compiling the file first.  In this scenario, they were able to create an ACCDE file on their machine, but were unable to use it on any other machine and received the same error message as Adam.  After we manually compiled it and then made an ACCDE file, everything seemed to work as expected.  It may not work in this situation, but it’s worth a try.

Best Regards,

Nathan O.

Microsoft Online Community Support

Answer 2

That's the article I mentioned as well.

Creating an ACCDE always compiles the application. How else would it remove the source code and leave the user with a working (compiled) app?

Answer 3

I’m not sure if this is the article you read, but if not, I would recommend reviewing it.

2533794          Error message when you run a compiled Microsoft Access MDE, ACCDE, or ADE file in Access 2010: "The database cannot be opened because the VBA project contained in it cannot be read"

http://support.microsoft.com/default.aspx?scid=kb;EN-US;2533794

In addition to this, what happens if you actually try and compile your database file before you make it into an ACCDE file?  To do this, you can do the following:

+>Open your Access database.

+>Press Alt + F11 to open your VBA window.

+>Click on the Debug menu and then select Compile. 

+>After you do this, recreate your ACCDE file and test.

Best Regards,

Nathan O.

Microsoft Online Community Support

Answer 4

Thanks for the reply Tom.

The database is in a trusted location.  I even tried it with the sample "Northwind" database and the same error came up. 

When I make the accde file, I copy it to a server directory. After that I opened it on my machine (win7) with no error.  When I go to open it on a XP machine I get the error.  Then when I come back to it on my win7 machine, and open it again, the error comes up on my machine as well.

The database operates as normal with the other accdb file extension.  No problems at all with either FE or BE on any machines in the building.

Our version of Access is 32 bit - 14.0.6106.5005

How would I go about a repair on Office?  I would have to do that to 40 machines...  Personally I doubt that's the issue as we haven't had Office 2010 for much more than a year and no other problems have been reported.

Thanks again,

Adam

Answer 5

You could try "Repair" of your Office installation. See help file for details.

Personally I would repeat your steps on another machine. This is not normal.

Also note that KB articles like http://support.microsoft.com/kb/2533794 speak about the bitness of Office, not Windows. It is NOT recommended to install the 64-bit version of Office, unless you really, really know what you are doing. Of course if you truly have Win-32 you won't be on Office-64.

Is your database in a Trusted Location?