Deployment information needed for Access 2003

[Jennifer B.]

Hi Every Body:

I hope this is to the right post. I apologize if I am incorrect.

Could anyone please answer one or any of the following questions for
Access 2003:

- Maximum size of an Access database (after split)
- speed of Access using a Citrix server (any server for that matter,
will it affect the processing time of other database programs running
alongside Access.
- Would you suggest adding a separate server?
- networking issues if Access crashes on the server

I have my database already set up and am ready to start testing, but
first need to have some answers available for my boss.

I did spend 2 1/2 hours searching microsoft to no avail.

Thank you in advance to anyone that can help.

much appreciated

Jennifer

[Tony Toews]

je************* @msn.com (Jennifer B.) wrote:

Could anyone please answer one or any of the following questions for
Access 2003:

- Maximum size of an Access database (after split)
2 Gb.
- speed of Access using a Citrix server (any server for that matter,
will it affect the processing time of other database programs running
alongside Access.
No specific reports on Access 2003 and Citrix but A2000 works well on Citrix.
- Would you suggest adding a separate server?
No, a client has them happily running along side all the Office apps and such.
- networking issues if Access crashes on the server

Same as if it crashes on stand alone PCs.

My random thoughts on Microsoft Access, Terminal Server and/or Citrix
http://www.granite.ab.ca/access/terminalserver.htm

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

[Larry Linson]

"Jennifer B." wrote

Could anyone please answer one or
any of the following questions for
Access 2003:

- Maximum size of an Access database (after split)
Maximum size of an Access 2003 database is 2GB. The front-end should be on
each user's machine, or in each user's separate storage if you use Terminal
Services. Each back-end from which tables are linked can be 2GB. It is
almost certain that you'll find performance will be the limiting factor
rather than storage.
- speed of Access using a Citrix server
(any server for that matter, will it affect
the processing time of other database
programs running alongside Access.
That would be impossible to guess, even if you had provided reams of
detail... it depends on quite a number of factors unique to your
environment.
- Would you suggest adding a separate server?
See above.
- networking issues if Access crashes on the server

If you are running Terminal Services (or Citrix), both the front-end and
back-ends will be running on the server. There is always a possibility of
corruption when Access terminates "ungraceful ly" especiall in a multiuser
environment. Network issues, in the TS/Citrix case, are not as big an issue
as in a normal LAN multiuser environment where the front end resides on the
user's machine and the data on the server.

In the LAN setup, the most common provable cause of corruption is dropped
network connections, in my experience and observations.

The best collection of detailed information on multiuser performance and
avoiding corruption is MVP Tony Toews' site,
http://www.granite.ab.ca/accsmstr.htm.

Good luck with your project. Be sure to give each user their own copy of the
front-end -- multiple users logged in to the same front-end or monolithic
database significantly increases your chances of corruption.

Larry Linson
Microsoft Access MVP