G
Guest
I have been using Access with SQL Server and ODBC linked tables for the past
10 years or so with few problems, even with 100+ users, each with a PC
containing their own copy of the front-end mdb.
I am doing some work now in which the above works fine, but when the mdbs
(one for data entry, one for reporting) are transported into the Citrix
environment, there is no end of problems with timeouts, ODBC-call failures,
disk or network error messages etc. Of course the users are very frustrated.
The data entry application is code-intensive, with unbound forms and data
access classes for validation and update to SQL Server, so the load on a
Citrix server should be very light. The database has about 25 tables, non of
them large in terms of either columns or rows. The data entry application is
about 6MB, with 40+ forms.
I have no prior experience with Citrix. What key questions do I need to ask
the Corporate Citrix administrators to get on the right track?
10 years or so with few problems, even with 100+ users, each with a PC
containing their own copy of the front-end mdb.
I am doing some work now in which the above works fine, but when the mdbs
(one for data entry, one for reporting) are transported into the Citrix
environment, there is no end of problems with timeouts, ODBC-call failures,
disk or network error messages etc. Of course the users are very frustrated.
The data entry application is code-intensive, with unbound forms and data
access classes for validation and update to SQL Server, so the load on a
Citrix server should be very light. The database has about 25 tables, non of
them large in terms of either columns or rows. The data entry application is
about 6MB, with 40+ forms.
I have no prior experience with Citrix. What key questions do I need to ask
the Corporate Citrix administrators to get on the right track?