How do you create a free runing program in Access?

[HT]

I understand there is a way to create a program in Access that a user does
not need Access in order to run.
Does anyone know how?

 

[Daniel Pineault]

If you build an ms access database with an ms access front-end, then you need
access to run it.

That said, microsoft has made available its runtime version for deployment.
Which mean in plain english, if your user only need to run your db and do not
require the ability to modify objects, vba code... then they can freely
download and install the runtime version and they will be able to run your
database.

If however, your users require the avanced abilities mentioned above then
they must have a full blown copy of ms access at their disposal.

You can check out the runtime version a
http://www.microsoft.com/downloads/...d9-9dc6-4b38-9fa6-2c745a175aed&displaylang=en
--
Hope this helps,

Daniel Pineault
http://www.cardaconsultants.com/
For Access Tips and Examples: http://www.devhut.net
Please rate this post using the vote buttons if it was helpful.

 

[John W. Vinson]

I understand there is a way to create a program in Access that a user does
not need Access in order to run.
Does anyone know how?

You understand incorrectly. A database is not a program and cannot be turned
into a program, and it must have some version of Access on the user's
computer. But you don't need to buy the full Access program!

What you *can* do is obtain the appropriate Access Runtime version, and
provide it (free of charge) to users to run the database. See
http://www.granite.ab.ca/access/developereditionversions.htm
for the version appropriate to your version of Access. The 2007 runtime is
free (unlike earlier versions) and will work with 2000 and later format
databases.

 

[Mark Andrews]

From what I have found, there are a few commercial programs out in the
market built entirely from access. the usual steps are:
- create a front and back-end database
- change the front-end to an MDE or ACCDE file (to stop users from getting
into it)
- it will run with the access runtime (found various ways depending on which
version of access you are using)
- I have found you usually need sagekey to create the install program (also
need license agreement, icon etc...)
Otherwise for example if your application is access2007 and the user has
office 2003 the two version of access will
do the usual "not getting along well" types of behaviors (such as those
configuring office messages you might see if you switch
between the 2 versions).
I have a brief article on my experience with sagekey for my last commerical
application built in access:
http://www.rptsoftware.com/help/microsoft_access_thirdparty/sagekey.asp

Your other option is to use a different tool such as .NET to build the
front-end application (more work usually but
can sometimes get a slightly better application in my opinion). I have
opted for using Access for everything.

HTH,