How do I create a Access Run Time version?

  • Thread starter Thread starter Eric
  • Start date Start date
E

Eric

I am going to try and make a Access Run Time version of
our databases, but don't have a clue as to HOW to make
a .mdb file into a Access Run Time Version. I am going to
be using a dummy .mdb file so I don't do anything with our
current .mdb files.

I am using Access 97.
 
You don't "make a .mdb file into a Access Run Time Version".

What happens when you have the Developer version of Office is that you can
package your application together with a royalty-free run-time version of
Access. Users who don't have Access installed can install the run-time
version, and then they'll be able to use your application. Your application
isn't changed in any way, shape or form.
 
Eric said:
I am going to try and make a Access Run Time version of
our databases, but don't have a clue as to HOW to make
a .mdb file into a Access Run Time Version. I am going to
be using a dummy .mdb file so I don't do anything with our
current .mdb files.

I am using Access 97.
Click to expand...

The runtime is a special installation of the Access executable. It is not
something you "do to your file". In fact your mdb is not altered in any
way at all when you distribute with the runtime versus running it with a
licensed version of Access.

Think of the runtime this way. Microsoft makes money selling Access. You
develop something in Access that you want people who have not purchased
Access to be able to use. So Microsoft says "Ok, we'll provide you with a
version of Access that can run mdb files, but cannot be used to develop
them and we'll give you tools and license to give this version of Access to
anyone you want." This way your users are given a "free" version of
Access, but they can't use it for anything except to run existing files.

So, a typical runtime installation program installs the Access runtime (if
the same version of Access is not already present), your mdb file and any
other supporting files you choose to include, and it creates some
shortcuts. The included mdb file is the same exact file you currently have
on your PC now.

Now, a file that is to be used in the runtime environment has to be set up
appropriately because the runtime environment does not provide the same
interface as a licensed version of Access. None of the built in toolbars
or menu bars will be there and there is no access to the db window. You,
as the developer have to provide all of the interface for the application.
You also have to have very robust error handling as most errors in the
runtime environment that are not properly handled by your code will end the
program.

I provide a runtime option for my distributed apps, but only as a "last
resort". I recommend that my users purchase and install a licensed version
of Access because there are a LOT less problems working in that environment
compared to the runtime. The runtime (at least in A97) is fairly well
behaved on PCs with no other version of Access installed, but can cause a
lot of "issues" when installed alongside other versions of Access. Some of
these are merely irritating and some are fairly substantial. In addition,
the cost of the developer's tools (time, money, and extra work) is high
enough that no savings will be realized over purchasing full-blown Access
unless you distribute to at least "several" PCs.
 
I think your missing my point...HOW do I package it into a
Access RunTime application?
 
Back
Top