Multiple Front Ends on SERVER??

[Mike MacSween]

The application is at present a 'classic' FE on each workstation, BE on
server split. Both Access 2000. Windows 2000 Server server, Win 2K pro
workstations.

1. I've been getting quite a few 'Disk or Network error' messages. On
various machines.

2. And also some 'cannot find the field blahblah referred to in your
expression'. I suspect that the second message is also a network error.

The network engineer seems experienced and has tried to solve the problems.

I'd like to see if 2. above is actually a network problem, and also let the
users carry on working without errors until I've got to the bottom of this.

So, I know this is all 'wrong' I thought about putting several copies of the
front end on the server, one for each user.

This problem tends to be compounded because my standard error routine logs
errors to a table on, yes, the server. So if the error is caused by loss of
connectivity they get a circular series of error messages.

Whaddya think about putting the FE on the server.

There are 8 users in total, and only 5 regular users, and even then probably
at one time there will be no more than 3 actually using the database. It's
not data instensive.

Cheers, Mike MacSween

[Tom van Stiphout]

On Thu, 9 Sep 2004 12:20:26 +0100, "Mike MacSween"
<mi******************@btinternet.com> wrote:

This setup would only improve matters if the users would use Terminal
Server or similar to run sessions on the server itself. Otherwise,
when they open the FE on the server, it will be copied to memory on
their workstation, and connect to the BE over the network,

-Tom.

The application is at present a 'classic' FE on each workstation, BE on
server split. Both Access 2000. Windows 2000 Server server, Win 2K pro
workstations.

1. I've been getting quite a few 'Disk or Network error' messages. On
various machines.

2. And also some 'cannot find the field blahblah referred to in your
expression'. I suspect that the second message is also a network error.

The network engineer seems experienced and has tried to solve the problems.

I'd like to see if 2. above is actually a network problem, and also let the
users carry on working without errors until I've got to the bottom of this.

So, I know this is all 'wrong' I thought about putting several copies of the
front end on the server, one for each user.

This problem tends to be compounded because my standard error routine logs
errors to a table on, yes, the server. So if the error is caused by loss of
connectivity they get a circular series of error messages.

Whaddya think about putting the FE on the server.

There are 8 users in total, and only 5 regular users, and even then probably
at one time there will be no more than 3 actually using the database. It's
not data instensive.

Cheers, Mike MacSween