Need help on distributing data base

[NielsE]

I have developed a data base to be distributed to 10-15 users who do not
have Access installed. I have the Sccess 2003 Developer Extensions and can
thus package a runtime version.
I guess that the best thing to do is to split the db in a back-end db with
the tables to be installed on the server, and a front-end db to be
distributed to the users. I have made a few attempt to do this but without
much luck. Therefore a few questions:
1) Do I have to pack the back-end db as a runtime vesion or can I install
just copy it as it is to the server?
2) Since users do not have Access I take it that the front-end db under all
circumstances have to be packed with Developer Extensions. However, does it
have to a mdb file or can I use the a mde file?
3) In one of the fruitless attempts I have made so far I got an error
message:"The expression on-timer you entered as the event property setting
produced the following error: Disk or network error" (I use the on-timer
event to close the opening form and open the switchboard).
Any help would be appreciated.
Niels

 

[Brian]

1) The back end does not need to be installed. The single .mdg file can
simply be copied to a server, even one that has no version of Access
installed.

2) As an alternative to having the users install your application, you can
set up a distributable package once but send the users just the Access
runtime installation files from the package (AccessRT.msi, AccessRT.cab, &
the Setup subfolder, I believe). This will install just Access runtime, not
your application. Just be sure to include a copy of the front end (.mdb or
..mde) and instructions telling the users to place it wherever they like on
their local hard drives.

3) Here is the typical problem, though. The users' path to the back end may
differ from the path you used when setting up the front-end/back-end link, or
even from each other. For example, you may set up the links while both the
front end & back end are on your hard drive, but the users will likley be
sharing the back end via a mapped drive to a network share. Thus, the links
you set up will be invalid for them.

If you know that everyone will use the same path to the back end (i.e. using
the same mapped drive), just make sure that you use the same path when
linking the tables, and it should work. (I would guess that this is the
answer to your #3 question)

If you cannot guarantee the same path, then you will need to write code to
check for valid table links and, if none are found, allow individual users to
browse for the back end (using a Windows API call). I can post code if you
need it.

 

[NielsE]

Thanks Brian, this was very helpful.

I am now trying to simulate the install on my small home network (will later
install it on my work place network). It works ok so far.
However, how do I link the front-end to the back-end before packaging the
front-end into a run-time version using the correct mapping on my work
network? (I have to do this at my home network since the Access developer
extension is on my home PC). When I try to enter the mapping (using the Link
Table manager) that will be used on the work network, I get the message that
the path is not correct, which, of course, is logical since this does not
exists on mu home PC. Is there a way to force a link that does not exist?
I have then tried to figure out if I could re-link the tables when the
run-time front-end version is installed, but this does not seem possible due
to the limited possibilities available in the run-time version.
Any help would be appreciated.
Niels

 

[Brian]

You can map a drive to your own computer that is the same drive letter that
is used on the work network, and then link tables using the mapped drive. For
example, if the users have a P: drive mapped to:

\\server_name\AppsFolder\YourApp (where AppsFolder is the name of the shared
folder)

Then their path to the folder will be P:\YourApp.

Now, make a folder on your own hard drive such as this:

C:\Documents and Settings\...\Programming\YourApp

Share the Programming folder. The name of the shared folder does not need to
match the one at the office; just the drive letter and the path following the
drive letter.

Put your application in the YourApp folder
Map your P: drive to the shared Programming folder so that your path to the
backend MDB is P:\YourApp

Now, copy your backend data MDB to the YourApps folder and set up your links
to it using the P:\YourApp path, which is the same path the users at the
office will use. If you have two computers at home, you can also just copy
your backend MDB to another computer and map the drive to the second computer.

If you want the code that allows each user to browse for the path and
re-link, even from within an MDE and/or runtime version, just reply to this,
and I will post it for you. It uses the Windows API browing call instead of
menu options.

 

[Brian]

You can also just write VBA code to create all the linked tables, but that is
a LOT more work than just simulating the office network by mapping a drive to
your own computer.

By the way, last time I tried it, the drive mapping to my own computer could
be done only while it had a valid network connection; it would not work, for
example, when I had my Ethernet cable disconnected.

 

[NielsE]

Thanks once again Brian. I would be grateful if you could send me the code
and also tell me where exactly to put it.
Niels

 

[Brian]

Sorry about the delay; I was out of town on a business trip. Send me an
e-mail, and I will reply with the code & the form I use to allow the
browsing; that will be much easier than posting here, since it is rather
complex.

brainy
at
pacifier
dot
com

 

[Arnold R]

I have packaged an mde file with Access runtime. When my user installs it on
a computer that already has Access 2002 installed he gets a message
"<application> cannot install one of its required products. Consult your
technical support." I want to be able to distribute my application, with the
2003 Access runtime to people who may have Access 2002 or earlier installed
on their computers and in use for their own work. Is this possible?

Arnold R