Access with Thin Clients

  • Thread starter Thread starter GeorgeMar
  • Start date Start date
G

GeorgeMar

It is recommended that in a split database, that the Back
End resides on the server and that the Front End resides
on the local drive, to speed up processing and prevent
data corruption.

What happens in the case where the site runs Citrix and
only has thin clients? If the Front End resides on the
server, won't the same issues arise regarding speed and
data corruption?

Hope you can help!

many thanks
george
 
No, each user should still have their own disk space and their own copy of
the front end, it'll just be running on the server. Just using Citrix does
not mean you can safely have multiple users opening the same copy of the
front end.

See MVP Tony Toews' site, http://www.granite.ab.ca/accsmstr.htm for an
outstanding collection of information and links re: multiuser databases. You
might search for some posts by MVP Albert Kallal, who has offered a lot of
good pointers on Windows Terminal Services and Citrix with Access. He, too,
has a nice site with samples, but I don't have the URL handy just now.

Larry Linson
Microsoft Access MVP
 
Thanks for the pointers. I'll follow them up.

many thanks
george
-----Original Message-----
No, each user should still have their own disk space and their own copy of
the front end, it'll just be running on the server. Just using Citrix does
not mean you can safely have multiple users opening the same copy of the
front end.

See MVP Tony Toews' site,
Click to expand...
http://www.granite.ab.ca/accsmstr.htm for an
 
George,

I presume you are talking about multiple users? There are a number of
advantages to a split database scenario... but "speed up processing" is
not one of them. In fact, you will see a significant drop in performance.
 
Back
Top