Multi Terminal Linking

[Steve]

Make a frontend that links to the backend and install a copy of that
frontend on each computer.

PC Datasheet
Providing Customers A Resource For Help With Access, Excel And Word
Applications
(e-mail address removed)

 

[Marshall Barton]

When I have a seperate Front end for each computer and one Backend
located on the server, how do I link all of the seperate front ends to
the server backend? Do I do each machine seperately?

Use the Linked Table Manager (under Tools - Database
Utilities menu item) to link a front end to the back end.

If the path is the same for all front end machines, then you
can do it once on the front end before you copy it to all
the user machines.

If the user machines use different drive mappings, then you
will have to do it on each user machine after copying the
front end.

 

[Douglas J. Steele]

If you can't be certain that all users have their drives mapped the same
way, you can always use a UNC (\\server\share) rather than a drive letter
when referring to the back-end.

To use a UNC via the Linked Table Manager, navigate to the back-end through
the Network Neighborhood, rather than through the mapped drive.

Once you've done that, you should be able to give each user a copy of that
front-end, and no relinking should be required.

 

[Guest]

Each front end has to be linked to the back end. As Steve said, you can
create the link on your computer and distribute to other users on the
network. The one issue you need to be aware of is drive mapping.

It may be that not all users have the same drive mapping. That is, that all
users will have drive G: mapped to the back end folder. The best way to deal
with that is to use UNC paths rather than Drive Mapping. That is mapping the
server and path, for example:

\\SomeSerer\SomeFolder\MyApplication

This will ensure that it will work for all users regardless of drive mapping.

 

[DS]

When I have a seperate Front end for each computer and one Backend
located on the server, how do I link all of the seperate front ends to
the server backend? Do I do each machine seperately?
Thanks
DS

 

[Albert D. Kallal]

The backoffice also has Raid5. So everytime a record is written I have

the record written to both backend databases.

Right, but if due to a network glitch, and you corrupt the back end
database, then your mirror will simply "mirror" that corruption. I suppose
having a mirror is great if one hard drive goes down, but, if a user were to
delete the file, then the mirror would also simply follow that and delete
the file also.

I am also using all unbound forms.

why? For what reason would you waste all that time and resources? While vb6,
or vb.net has great tools for un-bound forms (all kinds of wizards etc),
ms-access has NO provisions for un-bound forms, and has no wizards. Further,
by using un-bound forms, you loose the ability to use the on-dirty, before
update, after update..and a bazillion events designed for data bound forms.

When you drop bound forms, you can't use 99% of the forms features, and you
have no wizards or data connecting systems like you do in vb. Essentially,
your backed yourself into a corner, dropped all of the productive tools
built into ms-access, but replaced them with nothing that saves you
development cost.

You basically increased the cost of development beyond that of using
standard tools. In effect, you wasting company resources and time..or simply
money that could be used to feed the poor.

ms-access is about the worst choice when you use un-bound forms, and further
it don't reduce corruption, and generally does not increase performance
either....

 

[DS]

Make a frontend that links to the backend and install a copy of that
frontend on each computer.

PC Datasheet
Providing Customers A Resource For Help With Access, Excel And Word
Applications
(e-mail address removed)

Sounds good to me!
Thanks
DS

 

[DS]

DS wrote:





Use the Linked Table Manager (under Tools - Database
Utilities menu item) to link a front end to the back end.

If the path is the same for all front end machines, then you
can do it once on the front end before you copy it to all
the user machines.

If the user machines use different drive mappings, then you
will have to do it on each user machine after copying the
front end.

Thanks Marshall, Heres what I have..

BackOffice Term1 Term2 Term3
FE.mdb FE.mdb FE.mdb FE.mdb
BE.mdb
CR.mdb

Basically all terminals and the backoffice are connected to BE,mdb which
is the Backend and CR.mdb which is a second copy of the backend in case
the backend gets corrupted. So all of the terminals and the backoffice
are linked to two backends. The backoffice also has Raid5. So
everytime a record is written I have the record written to both backend
databases. I am also using all unbound forms.

Thanks
DS

 

[DS]

If you can't be certain that all users have their drives mapped the same
way, you can always use a UNC (\\server\share) rather than a drive letter
when referring to the back-end.

To use a UNC via the Linked Table Manager, navigate to the back-end through
the Network Neighborhood, rather than through the mapped drive.

Once you've done that, you should be able to give each user a copy of that
front-end, and no relinking should be required.

Great Thanks, Douglas. I think, I hope I'll have this worked out by the
end of the day!
DS