Hard time trying to 'Package Solution' - Access 2010 on Win 8.1 pro 64

Question

I got myself a brand new system (win 8.1 pro 64) a while ago, and with it,
got a few problems as well. - If it makes any difference, I had an accdr and changed file extension to accdb, this is
the  FE  I'm trying to 'Package' now - 
It happens that after installing Office Professional Plus 2010(not sure if
x86 or x64 - does it matter?), checking all the conditionals for MSAccess, 
even repairing installation a bunch of times, no matter what, 
whenever I try to 'Package Solution', there's always a boring message 
at the end stating that, 'An unexpected error has occurred', period. 
That's it!
I tried to move my files to documents folder, assuming that might be
caused by lack of permission, still nothing happens, other than the same
'An unexpected error has occurred', no additional info available.
Googling this, I could find one or another info, but people usually report
in common with my issue, just the error message, the whole context seems
to be pretty different. Anyway, never been thru such a thing, don't know
if I should install any hotfix, I reinstalled office a couple of times already,
nope! It's not working! 
And I got this app release that's been waiting almost 1 week now to reach my customer, 
in other words, big trouble! 
So, I really could use some help, and I appreciate anybody who would kindly
lend me a hand on the matter of this subject.
Sorry if that sounds stupid, and thanks in advance!

Answer 1

This is much I suggested using an accDE. You use the accDB to develop and create the application. When you compile to an accDE, then users cannot see or view VBA code, nor can they change reports or forms if they get “inside” the application.
So you most certainly will continue to use and develop using the accDB, but the “last” step before deployment is to first ensure you VBA code compiles (in the VBA editor, go debug-> compile). Once your sure code compiles, then you create the accDE that
you will include in your package to distribution to users. Do keep in mind that this suggest thus suggests your data is “split” or outside of the application you package else updates to users would overwrite their data.
So using an accDE means users cannot modify forms/reports, and also means that users cannot view code. This also eliminates the need for some kind of password system to prevent modifications to the application. so you can rename the accDE to a accDR, but
even if users re-name it back to a accDB or accDE, modifying to forms/reports and VBA code is NOT possible. This also means you do NOT want to lose your accDB that you are using for development.
I explain this concept of a split database here:
http://www.kallal.ca/Articles/split/index.htm
Regards,
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada