Minimizing chances of data corruption.

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

My understanding of the consensus for a SOHO on a local LAN is:
1. Split database.
2. Data is on server (or ordinary PC)
3. MDE file on EACH user PC.

However I have just added Windows Server 2003 running Terminal Services (in
order to access the application remotely over the internet) to the workgroup.
This works extremely well, well beyond my wildest dreams.

This necessitates that a copy of the MDE sits on the server. So I wondered
what the speed of the application would be if the local users used Terminal
Services over the LAN.

The speed increased by 3 to 5 times or more. By 'speed' I mean going from
record to record in a single record complex form.

So, if I get my 5 local users to use TS it would 'break rule 3' above.

Do I go for it?
 
I would say, most certainly go for it!

You could/should copy the FE to each user's home folder in their TS
session. It would be just like giving each of them their own copy on their
local computer.

This is probably a very good solution for remote sites to use a common BE
database, as the FE is in the same place as the BE. If a user loses their
remote connection (which is apt to happen over a WAN), the FE connection to
the BE is not broken, just the user's connection to the Remote Desktop.
Thus, the chances of data corruption due to the FE being rudely severed
from the BE is greatly reduced.

And an added benefit of the data flow from the BE to the FE being on the
same LAN (that you've already seen), is access times to the data being
amazingly quick. The only data that's being sent across the WAN are the
screen updates, which is a relatively small packet of data.
 
My understanding of the consensus for a SOHO on a local LAN is:
1. Split database.
2. Data is on server (or ordinary PC)
3. MDE file on EACH user PC.
Click to expand...

Yes, the above works very well. I have clients that have been running 3-5
users, quite heavy use, and none have had problems in about 5 years worth of
use. 5 users x 5 years = 25 years of use....
However I have just added Windows Server 2003 running Terminal Services (in
order to access the application remotely over the internet) to the
workgroup.
This works extremely well, well beyond my wildest dreams.
Click to expand...

Yes, TS really is a very nice technology.
This necessitates that a copy of the MDE sits on the server. So I wondered
what the speed of the application would be if the local users used
Terminal
Services over the LAN.
Click to expand...

They would see the same performance as the remote users, which in fact is
quite good, since NO data travels down the network...it is all local.
The speed increased by 3 to 5 times or more. By 'speed' I mean going from
record to record in a single record complex form.
Click to expand...

The above is great. However, in fairness, you should not see that much of a
increase. I would test the idea of a persistent connection. This means in
your startup code, you OPEN a table, and keep it open (now try running the
application, and see if the delay goes away. Note that this persistent
connection only applies to the machines (front ends) that connection OVER
the network. You should be able to get the speed of the users version up to
the same speed as the one that runs on the server. However, if this trick
don't help, then you can/could resort to using TS for all users (I would try
and fix the code/performance here first..but you can go the TS way).
So, if I get my 5 local users to use TS it would 'break rule 3' above.
Click to expand...

No, in fact, many companies use thin client (remote desktop) for all their
computers. No more installing software on each pc, and each new upgrade
means you can continue to use "old" hardware. I know of a company that will
NOT sell their used 90mhz old Pentium boxes, but yet they just rolled out
the new version of office xp and windows xp to all the computers..and not
ONE SINGLE computer in the office had to be upgraded, as ALL computers run
remote desktop for everything. In many corporate environments, TS is a great
solution.

However, even when you use TS, then you STILL MUST give each user that logs
on their OWN copy of the mde. This is usually quite easy, as each logged on
user gets their own folders etc. So, you are NOT to break rule #3, and each
user of TS should get their own copy of the FE, and if ignore this, then you
risk increased frequency of corruptions. So, the rule of NOT allowing more
then one user into the same FE still applies.

And, note that Tony's free auto front end updater (that automatically copies
any new version to each workstation) also works correctly for TS.

You can find it here if you are not already using it:

http://www.granite.ab.ca/access/autofe.htm
 
Back
Top