By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,836 Members | 1,735 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,836 IT Pros & Developers. It's quick & easy.

Deploying access database

P: n/a
Hello All,

I had some considerable help from people in this forum a log while ago
whilst developing a databse for use in our business. The database has
developed beyond my wildest dreams over the last 3 years and I am very
proud of it.

It was developed in Access 2000 on a Windows 95 machine where it still
runs and during the development process I added various elements from the
installation disks which were not part of the standard installation.

I now wish to transfer the front end of this database onto 3 new computers
in the office with the backend on a server.

My problem is that the original MS Office 2000 Professional installation
disks have gone astray during our office move and I cannot therefore
install the add-ons which were not installed during the standard
installation.

Can someone please explain to me what I need to do to package the
application so that it will run on other computers which don't have the
full Access 2000 installation?

Any advice would be greatly appreciated.

Many thanks.

Malcolm Webb
Nov 13 '05 #1
Share this Question
Share on Google+
5 Replies


P: n/a
Malcolm:
In order to install and Access application onto a computer that does
not have Microsoft Access installed on it, you would have to create a
run-time installation. In order to do that you would have to have the
"Microsoft Visual Studio Tools for the Microsoft Office System" which
would cost you several hundred dollars.
This software has a wizard that would generate an installation image
which would install your Access application just as if you had
purchased it in a store.
The version I have is the 2003 version which works on the 2000 versions
of Access applications as well. Once the conversion is complete, I burn
the files it created onto CDs.
If you have any further questions about the product you can find me at
bear999 at gmail dot com.
Ted

Nov 13 '05 #2

P: n/a
It sounds to me as if you have Access installed on your other 3 machines,
but not all the "add-ins" from the installation disks.
Here's an approach which may work, although it's not for beginners...

Copy your "front end" mdb file to a new computer.
Open it in Access.
If it balks immediately, you may need to hold down the shift key while
opening it.
Open any code window, and click Tools - References.
You'll notice that several items are marked MISSING.
Make a note of these items.
Now go back to your machine, and open Tools - References.
Note the location of each of the files which was MISSING on the new
machine, and copy each one (via network or floppy disk) to the new machine.
Now you'll need to register each of the files you've copied on the new
machine.
From the Start button (lower left of your Windows screen), click Run.
In the box that pops up, type "regsvr32.exe" (without the quotes),
followed by a space and the full path/filename of one of the transferred
files. Click OK; you should get a messagebox confirming the registration.
Repeat for each file you've transferred.

Try again to open the mdb on the new machine.
Do you know how to relink the front end to the back end on the server?

Post back if you need more help.
"Malcolm Webb" <mf****@btinternet.com> wrote in message
news:me************************@mfwebb.compulink.c o.uk...
Hello All,

I had some considerable help from people in this forum a log while ago
whilst developing a databse for use in our business. The database has
developed beyond my wildest dreams over the last 3 years and I am very
proud of it.

It was developed in Access 2000 on a Windows 95 machine where it still
runs and during the development process I added various elements from the
installation disks which were not part of the standard installation.

I now wish to transfer the front end of this database onto 3 new computers
in the office with the backend on a server.

My problem is that the original MS Office 2000 Professional installation
disks have gone astray during our office move and I cannot therefore
install the add-ons which were not installed during the standard
installation.

Can someone please explain to me what I need to do to package the
application so that it will run on other computers which don't have the
full Access 2000 installation?

Any advice would be greatly appreciated.

Many thanks.

Malcolm Webb

Nov 13 '05 #3

P: n/a
<It sounds to me as if you have Access installed on your other 3 machines,
<but not all the "add-ins" from the installation disks.
<Here's an approach which may work, although it's not for beginners...

This is exactly the situation. Your explanation regarding the references
worked a treat. Thanks very much.

As for linking the tables to the server -- yes I know how to do that, but
the Linked Table Manager is not installed on the 3 other machines. I need
the original installation disks for that.

The Linked Table Manager is installed on my 10 year old Windows 95
computer which is failing fast, and I have made the link between the front
end and the back end on that machine and then copied the front end to the
other 3 machines. Everything works as it should -- well, nearly, but I
know how to resolve the outstanding issues.

Would there be any major rewriting of code needed to migrate this database
onto a later version of Access than 2000?

Many thanks.
Malcolm Webb
Nov 13 '05 #4

P: n/a
While the Linked Tables Manager is convenient, you can also relink each
individual table using File - Get External Data - Link Table.
And if you create the same mapping from each local machine to the server (so
that each machine "sees" the back end, for example, at
Z:\AccessStuff\MyBackEnd.MDB, then once you have one copy correctly linked,
you can just copy it to the other machines and the links should work.

I haven't worked much in Access versions above 2000 myself, but I think in
general anything that works in 2000 should work in later versions. (I've
heard of exceptions, but these don't seem to be major...)

"Malcolm Webb" <mf****@btinternet.com> wrote in message
news:me************************@mfwebb.compulink.c o.uk...
<It sounds to me as if you have Access installed on your other 3 machines,
<but not all the "add-ins" from the installation disks.
<Here's an approach which may work, although it's not for beginners...

This is exactly the situation. Your explanation regarding the references
worked a treat. Thanks very much.

As for linking the tables to the server -- yes I know how to do that, but
the Linked Table Manager is not installed on the 3 other machines. I need
the original installation disks for that.

The Linked Table Manager is installed on my 10 year old Windows 95
computer which is failing fast, and I have made the link between the front
end and the back end on that machine and then copied the front end to the
other 3 machines. Everything works as it should -- well, nearly, but I
know how to resolve the outstanding issues.

Would there be any major rewriting of code needed to migrate this database
onto a later version of Access than 2000?

Many thanks.
Malcolm Webb

Nov 13 '05 #5

P: n/a
File/Get external data/Link tables

I never knew that:-)

My problems are solved

A thousand thankyous to all who helped.
While the Linked Tables Manager is convenient, you can also relink each
individual table using File - Get External Data - Link Table.
And if you create the same mapping from each local machine to the server
(so that each machine "sees" the back end, for example, at
Z:\AccessStuff\MyBackEnd.MDB, then once you have one copy correctly > linked, you can just copy it to the other machines and the links should work.


Malcolm Webb
Nov 13 '05 #6

This discussion thread is closed

Replies have been disabled for this discussion.