Deploy

  • Thread starter Thread starter Adrian Brown
  • Start date Start date
A

Adrian Brown

Now i may be being very stupid here, i have office 2003 professional. Ive
written an access database, its split into FE and BE. I can find very
little information (ideally a step by step guide) to deploying the database
now its created. Ive got the runtime from the professional cd, thats fine.
But how do i go about setting the correct link on the BE tables. Its always
looking where they are on my development drive. What else should i be doing
when depolying a database?

Adrian
 
Adrian Brown said:
Now i may be being very stupid here, i have office 2003 professional. Ive
written an access database, its split into FE and BE. I can find very
little information (ideally a step by step guide) to deploying the
database now its created. Ive got the runtime from the professional cd,
thats fine. But how do i go about setting the correct link on the BE
tables. Its always looking where they are on my development drive. What
else should i be doing when depolying a database?

Adrian
Click to expand...
 
Sorry about the empty post... a slip of the mouse...

I'm not an expert, but I'll try to help. Normally, the BE resides in a
shared folder on the network server. The FE should point to this location.
Please note that it is preferable to use the UNC address (i.e.
\\servername\foldername\BE.mdb), rather than a mapped drive letter, since
mapped drive letters can vary from computer to computer. So, step-by- step:

1. Create a folder on the network server to hold the BE, and place the BE in
the folder.
2. Open the FE, and link the FE to the BE. Enter the the UNC manually, or
navigate to the BE using "Network Neighbourhood" in the Linked Table
Manager.
3. Copy the FE to the workstation; it should find the BE.

This assumes that Access is installed on the workstation, either in the
runtime or full version, of course.
Also note, the folder for the back end must have complete read/write/delete
permissions.

Now, another aspect of this arrangement is distributing new/updated versions
of the FE to workstations. There are several ways of doing this. I use Tony
Toews' AutoFE Updater. If you would like more information about that aspect,
please post back.

HTH
Fred Boer
 
Ill give that a go. Yes i have a \\server\data\be_data.mdb - password
protected database. The AUto update thing sounds very useful. Whats the
best way about getting the Shift disabled etc and stopping hacking of the
FE. Is there an easy way to do all that and not accidently lock your main
database.

Adrian
 
Dear Adrian:

Ah, well... now you are asking about implementing the Access security model,
which is a whole 'nuther kettle of wet, slippery, flapping, hard to manage
fish! <g> Here are some links to get you started:

Security FAQ (the Security Bible):
http://support.microsoft.com/?kbid=207793

Jack Macdonald's Security Document:
http://www.geocities.com/jacksonmacd/AJMAccessSecurity.pdf

Lynn Trapp's Ten Security Steps:
http://www.ltcomputerdesigns.com/Security.htm

Joan Wild's Tips:
http://www.jmwild.com/security02.htm

I have only recently tackled Access security myself, and if I can give you
one essential warning: Please, please, work on a backup copy until you
*really* know what you are doing! :) In addition I'd suggest lurking about
in the microsoft.public.access.security newsgroup, if only to see what kind
of trouble you might be able to avoid. If you are like me and many, many
others, you are going to be getting to know some very nice, helpful people
with names like Joan, and Jack, and Lynn, and Jeff (and others!), as you
work your way through the process!

Good luck!

Fred
 
Back
Top