Access 2000 Runtime

  • Thread starter Thread starter Thick Mike
  • Start date Start date
T

Thick Mike

I have a small database written in Access 2000 which I want to install on the
laptops of travelling employees.
I understand a runtime version could be created and loaded without the need
for licences or Access installed on each laptop - is that correct?

I also understand a Developers kit is needed to create a runtime db but the
version for Access 2000 is no longer available.

What are my options?
 
Thick said:
I have a small database written in Access 2000 which I want to install on
the laptops of travelling employees.
I understand a runtime version could be created and loaded without the
need for licences or Access installed on each laptop - is that correct?

I also understand a Developers kit is needed to create a runtime db but
the version for Access 2000 is no longer available.

What are my options?
Click to expand...

The runtime was always free for users, but not for the developer
distributing it. That changed with Access 2007 which is a free download
from Microsoft.

You can either download the tools to package your app with the 2007 runtime
or you can just have your users download the runtime from MS directly and
all you need to provide is the file.

The 2007 runtime should run your 2000 file though you might find a few
things that need tweaking.
 
Thick Mike said:
What are my options?
Click to expand...

To add to Rick's posting also visit Microsoft Access (Office)
Developer Edition FAQ
http://granite.ab.ca/access/developereditionfaq.htm

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
Granite Fleet Manager http://www.granitefleet.com/
 
Thank you Rick and Tony.
Am I right in thinking the created app will include tables (both read from
and write to).
Also, if I subsequently make a change to, for example, a form and the newer
version is reloaded, will it over-write the data in the tables?
 
Thick said:
Thank you Rick and Tony.
Am I right in thinking the created app will include tables (both read from
and write to).
Click to expand...

Your app is your app. The runtime changes nothing about your MDB/MDE
file(s).
Also, if I subsequently make a change to, for example, a form and the
newer version is reloaded, will it over-write the data in the tables?
Click to expand...

Generally you distribute a split app. One file with just tables and one
file with everything else including links to the tables in the first file.
Since most revisions don't involve the tables you can replace the "front
end" file without affecting existing data.

If you make a change that does affect tables or if you distribute a non-
split application then yeah, existing data is lost unless you do something
to prevent that. This is relatively easy with a split app where you make
changes to table structures in a subsequent version. It is a lot more
difficult if you distribute a single all-in-one file.

Generally speaking monolithic applications are seldom used when you are
creating apps for other people to use. It is best to adopt the practice
where all apps are split.
 
Back
Top