Runtime vs regular install

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have an access database that is to be distributed to approx 50 people, most
of which do not have MS Access physically installed. I've learned a little
bit about this 'runtime' option I have, but I'm very new to it and can't seem
to find any information as to what the main differences are.

Can anyone list the differences between a full installation of Access versus
a 'runtime' version of a database? Specifically, what functionality will be
lost as a result? What will the user NOT be able to do in a runtime database
that can normally be done in a full install?

Thanks everyone!
 
In a nutshell, the users will not be able to modify or create any forms,
reports, or modules. They will only be able to use the database to do what
you designed it to do. In some respects, this is a bonus as it keeps fingers
out of your work.
 
if you as a habit have always built custom menus, and hide all of the
ms-access interface, for the most part, the you don't have to do anything
when you deploy using the runtime. Wile the runtime is not any more of a
difficult tool, the effort required to convert your existing application for
use with the runtime really depends on how well your application is
designed, and designed with non-access users in mind.

For example, most developers will realize after a fairly short time, that
you need to split your database. Of course, this then means that you will be
using the linked table manager on a daily bases. It also means that to
reduce frustration levels of your user base, you will conclude that it is
high time to write your own code that can re-link tables. This would mean
you grab both the file "browse" api dialog, and also the re-link table code
(both of which are available at www.mvps.org/access).

Another natural progression is have you been deploying mde's to your users?
Again, this is just simply a natural processing of a ms-access developer.
So, if you been deploying mde's to your users;...then once again, you are
more ready to use the runtime system.

So, the amount of work to use the runtime system actually approaches zero if
you been working hard at improving your ms-access skills, and done things
like provide custom menus, re-link code, and distribute mde. I had been
doing all of theses for years, and when I deployed using the runtime, I did
not have to change ANYTHING...

Here is some articles...

http://support.microsoft.com/default.aspx?scid=kb;en-us;842004

http://msdn.microsoft.com/library/d.../odc_ac2003_ta/html/odc_acbasicsofruntime.asp


I have a sample applcation that would work just fine with the runtime...you
can a link below;

You most certainly can, and should hide all of the ms-access interface. The
options to complete hide and keep people out of the ms-access interface can
easily be done using the tools->start-up options. Using those options allows
you to complete hide the ms-access interface (tool bars, database window
etc). Also, using these options means you do not have to bother setting up
security.

Try downloading and running the 3rd example at my following web site that
shows a hidden ms-access interface, and NO CODE is required to do
this....but just some settings in the start-up.

Check out:

http://www.members.shaw.ca/AlbertKallal/msaccess/DownLoad.htm

After you try the application, you can exit, and then re-load the
application, but hold down the shift key to by-pass the start-up options.
So, the only thing left for use with a runtime would be to split the
database, and convert to a mde..
 
Thank you both. These is a great help.

Albert D.Kallal said:
if you as a habit have always built custom menus, and hide all of the
ms-access interface, for the most part, the you don't have to do anything
when you deploy using the runtime. Wile the runtime is not any more of a
difficult tool, the effort required to convert your existing application for
use with the runtime really depends on how well your application is
designed, and designed with non-access users in mind.

For example, most developers will realize after a fairly short time, that
you need to split your database. Of course, this then means that you will be
using the linked table manager on a daily bases. It also means that to
reduce frustration levels of your user base, you will conclude that it is
high time to write your own code that can re-link tables. This would mean
you grab both the file "browse" api dialog, and also the re-link table code
(both of which are available at www.mvps.org/access).

Another natural progression is have you been deploying mde's to your users?
Again, this is just simply a natural processing of a ms-access developer.
So, if you been deploying mde's to your users;...then once again, you are
more ready to use the runtime system.

So, the amount of work to use the runtime system actually approaches zero if
you been working hard at improving your ms-access skills, and done things
like provide custom menus, re-link code, and distribute mde. I had been
doing all of theses for years, and when I deployed using the runtime, I did
not have to change ANYTHING...

Here is some articles...

http://support.microsoft.com/default.aspx?scid=kb;en-us;842004

http://msdn.microsoft.com/library/d.../odc_ac2003_ta/html/odc_acbasicsofruntime.asp


I have a sample applcation that would work just fine with the runtime...you
can a link below;

You most certainly can, and should hide all of the ms-access interface. The
options to complete hide and keep people out of the ms-access interface can
easily be done using the tools->start-up options. Using those options allows
you to complete hide the ms-access interface (tool bars, database window
etc). Also, using these options means you do not have to bother setting up
security.

Try downloading and running the 3rd example at my following web site that
shows a hidden ms-access interface, and NO CODE is required to do
this....but just some settings in the start-up.

Check out:

http://www.members.shaw.ca/AlbertKallal/msaccess/DownLoad.htm

After you try the application, you can exit, and then re-load the
application, but hold down the shift key to by-pass the start-up options.
So, the only thing left for use with a runtime would be to split the
database, and convert to a mde..


--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
(e-mail address removed)
http://www.members.shaw.ca/AlbertKallal
Click to expand...
 
Access Joe said:
I have an access database that is to be distributed to approx 50 people, most
of which do not have MS Access physically installed. I've learned a little
bit about this 'runtime' option I have, but I'm very new to it and can't seem
to find any information as to what the main differences are.
Click to expand...

Also right click menus don't exist.

Microsoft Access (Office) Developer Edition FAQ
http://www.granite.ab.ca/access/developereditionfaq.htm

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
 
Back
Top