I have an Access application with seperate front and back ends. All users
have their own front end. I am getting corruption in the back end.
Could this be caused by Citrix/TS forcing a logoff due to idle timeout? If
so then this could theoretically be replicated by logging off any
workstation (not a thin client) with the front end still open.
What about if the idle session is reset? That is different then logoff.
Any thoughts?
Andrew, I have an A2k db on our Citrix (split). At first I also had a
problem with the idle time log off and password logoff (after so many tries
the user is automatically exited). Once I removed them, the troubles went
away. I did not investigate it thoroughly to find out why. The idle time is
gone as it the password logoff. The password portion is still there, just
the number of tries was eliminated.
John
> I have an Access application with seperate front and back ends. All users
> have their own front end. I am getting corruption in the back end.
[quoted text clipped - 6 lines]
>
> Any thoughts?