Package Solution Wizard - Unexpected Error Access 2010, Access 2010

[Machinery]

Hello,



Hoping to find some insight into what is causing "An unexpected error has occurred" after I fill out the necessary information required by the Package Solution Wizard. As soon as I click "OK", I receive the error. I have researched this issue quite a bit and mostly come back with this being an Access 2007 problem. There is a work-around posted by MS Support within this link; http://support.microsoft.com/kb/940793. This however, does not solve my problem and I am using 2010. Additionally, there is a hotfix that is supposed to correct this issue for Access 2010 but installing it also did not solve my problem. I also have 2013 available to me but Package Solution Wizard was chucked out of existence.

When I open my database in Access 2010, "Database (Access 2007) - Microsoft Access" is displayed at the top of the app window. Since I created the database with Access 2010, I have always been confused why it appears this way and wonder if that could be a factor. I have tried saving as however, the db still opens as what I assume to be in 2007 format.

I have compiled, compacted and done everything I can think of to get around this issue but am stuck in simple minded frustration where someone is probably going to point out a simple solution that I have overlooked. Hopefully that will be the case anyway!

Any help is greatly appreciated as this is holding me back from deploying my db for its intent.

[ItsMe]

I do not believe Access 2007 Developer extensions are the same thing as the Access 2010 Package Solution Wizard. AFAIK the Package Solution thingy is unique to 2010.

As for why you are getting the error, it could be a myriad of things. Make sure all of the paths you type and settings etc. are correct.

As for Access 2007, 2010, and 2013... they all use the same file format, 2007.

The difference between the three flavors are the features available. If you want to employ a specific feature in your app, choose the correct version. The default format is the same.

[Machinery]

Thank you for the information. I take it that since they all use the same file format, 2007, then that is why I see "Database (Access 2007) - Microsoft Access" at the top of the app?

I have tried to ensure paths and settings are correct and can't seem to find any mistakes. I could be entering something wrong however, I have never used Package Solution Wizard before so I don't have a successful experience to baseline.

[ItsMe]

...Package Solution Wizard before so I don't have a successful experience to baseline...

You and me both. Perhaps you can practice with a dummy app. No linked tables no special files to associate. Keep everything local on your machine. You may have an issue with your Access install. This needs to be ruled out.

As for seeing "Database (Access 2007) - Microsoft Access" displayed everywhere, yes.

[Machinery]

Thanks for giving me some direction. I am able to package a blank database successfully so at least I know I am filling out all of the fields correctly and can rule out a bad install. Back to square one now, totally clueless. I have compiled and compacted and can't find any errors within my app. Do you have anymore ideas ItsMe?

[ItsMe]

You cannot package your app because when you move to the last step of the Wizard you get the error, "An unexpected error has occurred"? Is this correct?

If so, I would create a new, blank DB file using Access 2010. I would import all of the objects from an original Master File to your new DB. I would do this in a few steps. I would first import the tables, I would then Import the queries. I would create a copy of the new DB with tables and queries and Archive it. I would then import objects to a copy of the new DB, testing with Packaging Wizard until I reproduced the error. It sounds like a bad module in a form or report.

[Machinery]

Well ItsMe, you solved it! I can't explain why it works now but for whatever reason I just tried packaging my app again and it now does its job? I guess access needed a practice run with a blank db first... Weird.

Anyway, thanks!