MSARN200.EXE .v. MSACCESS.EXE

I have some clients running a custom built application (MS Access 2 database) which uses the MSARN200 runtime.  It works fine if used locally, or if used off the fileserver, but when this database is run in a Citrix WinFrame session  some of the screen updates (calculations) do not happen unless forced with the F9 key.  It would seem that if you are willing to wait long enough they will update, but this can take minutes or hours depending on the screen.

If the MSACCESS.EXE is used instead of MSARN200 the calculations are instant!

Does anyone know of the reason for this calculation lag, or have a suggestion as to how it might be combatted?

cdempseyAsked:
Who is Participating?
 
ChrisLewisConnect With a Mentor Commented:
Check the two INI files that are being used.  MSAccess will use MSACC20.INI, The MSARN200 will use a different INI file (Specified with the /INI parameter).

I'm sure that your [ISAM] or [ODBC] Sections are different.

Hope this helps

Chris
0
 
cdempseyAuthor Commented:
Both MSARN200 and MSACCESS are using the same INI file.  Still no resolution.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.