networking a data base

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Ted C. - 24 Jan 2006 16:20 GMT

I have created a data base for my company and now I would like to net work it
for thr33 work stations and a server. Can it be done. If so, How do i do
this?

Reply to this Message

Michel Walsh - 24 Jan 2006 16:30 GMT

Hi,

Make a backup.

Split the application (with the menu, Tools | Database Utilities... Database
Splitter, experiment with a dummy application, or with a backup, if you feel
uncomfortable). Place the Backend (the portion with the data), on a server
(be sure the server allows more than 10 concurrent network connections to
the "share" you will create). Also be sure to provide access to that share
from your network.

From ANOTHER PC, with the front end (the portion with forms and code),
relink your tables toward the network share (again, from the menu, Tools |
Database Utilities... Linked Table Manager ). Once done, distribute this
front end to the other PCs. You won't have to relink the tables (unless you
change of server for the backend portion).

That is relatively quite easy to do, in fact... it may surprises you how
simple it is, in the end.

Hoping it may help,
Vanderghast, Access MVP

>I have created a data base for my company and now I would like to net work
>it
> for thr33 work stations and a server. Can it be done. If so, How do i do
> this?

Reply to this Message

Karl H - 21 May 2007 14:44 GMT

Hi,

Regarding your advice on how to split the front & backends of a database,
does this work for applications that you package with Deveoper Extension
Package Wizard, too?

Are there any other tricks I should know about that?

Thank you,
Karl H

Reply to this Message

Douglas J. Steele - 21 May 2007 22:19 GMT

In my opinion, all Access application, even single-user apps, should be
split. This is because then you can easily make enhancements to the
application without impacting existing data.

When packaging with the run-time, only the front-end needs to be packaged.
The back-end is simply copied to the appropriate location on the server.

Signature

Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)

> Hi,
>
[quoted text clipped - 6 lines]
> Thank you,
> Karl H

Reply to this Message

Karl H - 21 May 2007 23:09 GMT

Hi,
What is the procedure for connecting the front end to the back end when you
have an MDE file on Access Runtime?
I didn't think there was much of an ability to modify the location of the
backend. During installation will the system ask for the location of the
backend files?
Is there a website that talks about this process? I have not found much
helpful information in the help files for Package Wizard.

Thank you so much for answering these questions!
Karl

> In my opinion, all Access application, even single-user apps, should be
> split. This is because then you can easily make enhancements to the
[quoted text clipped - 13 lines]
> > Thank you,
> > Karl H

Reply to this Message

Douglas J. Steele - 22 May 2007 22:22 GMT

Nothing will happen during installation.

You need to include your own code to check whether the linkage is correct,
and relink if not. http://www.mvps.org/access/tables/tbl0009.htm at "The
Access Web" is one way.

Signature

Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)

> Hi,
> What is the procedure for connecting the front end to the back end when
[quoted text clipped - 29 lines]
>> > Thank you,
>> > Karl H

Reply to this Message

Karl H - 24 May 2007 06:39 GMT

Hi,
I think I need a little more basic help, first. When I package the split DB
w/Package Wizard, I install under "typical install," or "custom," it doesn't
seem to give me the option of putting the tables in a different area than the
rest. When I explore the program files, this application has an mde file, the
help files, and a mdw system file.

How do you copy the tables to a server, with the packaged product? Is there
a good resource I could study for more information on this?

Thank you, again,
Karl

> Nothing will happen during installation.
>
[quoted text clipped - 35 lines]
> >> > Thank you,
> >> > Karl H

Reply to this Message

bob - 24 Jan 2006 22:48 GMT

The concept is simple and it works:

1. put the data in a back-end
2. give everybody a local copy of the front-end (which links to the
back-end)

Bob Galway

>I have created a data base for my company and now I would like to net work
>it
> for thr33 work stations and a server. Can it be done. If so, How do i do
> this?

Reply to this Message