linking vs importing

[shrndegruv]

Hey all

Lets say 2 people are each using a copy of an access application. Two people means data entry goes faster. Is it possible, when data entry is complete, to combine the results?

To do this, would one user import the other's database?

Also, is this conception of linking correct?: If I were to create tables, and only tables, and then save it as one mdb file, I could create a seperate mdb file that contained the queries,forms,reports,whatnot, by linking the second mdb to the first?

Thanx

 

[theprez]

Many people separate their applications into two MDB files. One a Front End w/ forms, queries, reports and modules. Two a Back End with nothing but tables.

You then link the front end to the back end tables. You can have multiple Front Ends linked to the same back end (maybe sitting on a server). This allows you to have multiple people working and further allows you to facilitate changes to the front end without stopping everybody. You can always replace the front end w/ changes. This can sit on individual workstations.

I usually write a routine to automatically link the tables for the user, but it can be done manually.

 

[shrndegruv]

to use multiple front ends for one back end, how do you set it up? Does the back-end have to actually go on a server, or can it just be a networked computer?

 

[theprez]

It can be on any shared resource, server or computer being shared. You really would have one front end, you just put separate copies on each workstation that needs to run the application. Then, you can manually link the tables from the backend.

Also, you may want to map a drive to the shared computer.

 

[Pat Hartman]

The be needs to be on a network drive that all the users have access to. If your network is peer-to-peer, that will be fine. The fe should be located on each individual's C: drive, not their network drive, to minimize network traffic.

To split the db, move the db to the directory where the be will remain. Then use the database splitter wizard. After the db is split, move the fe to a secure location for backup and send a copy to each user. The fe should be saved to the user's C: drive to minimize network traffic.

If each user maps the shared directory as a different drive letter, you'll need to take care of that before you distribute the fe. You'll need to use the linked tables manager to change the link to using the UNC name rather than a fixed drive letter. Instead of choosing the db by specifying drive/path, choose the shared drive from the network neighborhood icon.