Packaging an Access 2013 32 bit database for use with other computers that have the runtime 2013 version installed.

I need to package up and distribute an Access 2013 solution.
It is being developed on a 32 bit version of Access 2013, and at this point I want to make sure that I have a way to effectively distribute it.

I am aware that it should be split, but don't really understand how and where these separate files are stored.

Any direction on the steps needed to properly distribute this would be appreciated.
Please note that I am new to developing, so I appreciate the extra effort to provide step by step instructions.

Thanks All!
Dennis
DGWhittakerAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Kelvin SparksCommented:
The backend needs to sit in a "common" location, with the front end on local PC's (that's the ideal setup).

I use the Sagekey package for packaging and deploying accde's in this setup. (www.sagekey.com)

Kelvin
Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
Inno is another favorite of Access Developers, which is free, but you need to develop your own scripts.

It doesn't give you an isolated install either like Sage.   Check with Sage though; not sure if they've figured out the 32 vs 64 bit problem with Office.   You may need to installs.

and with all that said, you may not need an "install" at all.  If this is an internal distribution over which you have some control, all you really need is:

1. A link for them to install the Access Runtime.
2. A copy of the Front end and back end.
3. Copies of additional files.

  It's the last that is the kicker.  If you have .DLL's that need to be registered, registry entries to be made, etc, then it gets more complicated.  You can do all that manually or somewhat automatically (i.e. vbScript or batch file).

 If this is commercial or a large number of users, then Sage is well worth the price.

Jim.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
DGWhittakerAuthor Commented:
Thank You Gentleman! I will use this as I take the next steps.
Dennis
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.