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?