Access on CITRIX

Question

Anyone have some experience with deploying Access on CITRIX.

I have a mature split db which was running without any problems for several years which had now been deployed using CITRIX.  It now started giving odd errors.

When the user first logs in everything is fine, but after a certain period of time thing get weird.  The calendar start to fail an crashed the application completly, if the user tries to update different control it get an error stating that the operation cannot be perform at the present time.  All they have to do is log out and back in and they can do the very action that was generating the error?!

I know that CITRIX logs off inactive sessions, and does other things in the background and I have a gut feeling it has to do with a CITRIX setting, but don`t have any experience.  Does anyone have an idea what is going on, what is wrong?

QuestionBoy

Answer 1

That was my first sentence in my question. Yes, it is split. The back-end resides on a central server and then each user has an individual front-end copy of their own.

Everything was rolling fine, until the simultaneous migration to CITRIX and Office 2007 with the exception of Access Runtime which has remained at v.2002. When this change occurred, we started having intermittent problem when user are in the db for extended periods of time. When they first enter, it behaves perfectly, but after a while it starts to '**** out' resulting in random errors here and there. Sometime this control another time another control?! There doesn't seem to be much logic to the problems.

Answer 2

Do you have multiple users? Is the app split into front end/back end? Does each user have an individual copy of the front end?

Any app should be split, and no front end should ever be shared. The kinds of errors you describe are not atypical of shared front ends, in fact.