Screen Refresh Issue with Multiple Users

[BABSBINI]

Hi All,
Our application is a desktop application that can be accessed by multiple users by connecting over LAN or thru remote desktop sharing tools like Citrix.
Some of the screens have a refresh timer such that if user A has added data on that screen, user B should be able to see it after a fixed interval automatically. This works on most LAN networks. But often it happens that the screen for user C connected thru Citrix will never refresh! Thus C may add the same data as A, only to find that it has been duplicated after the saving process is complete.
C will be able to see the data added by A if he closes that screen (and sometimes the whole application) and opens it again.
There is no issue of access rights over here. All users have equal rights on the screens they are viewing.
Any suggestions as to what we should be looking at?
Thanx
Bini

 

[alvechurchdata]

Thus C may add the same data as A, only to find that it has been duplicated after the saving process is complete.

Are you using buffering or record locks here? I could see how an optimistic record lock might let this happen but row buffering or a pessimistic lock ought to prevent it.

Geoff Franklin

http://www.alvechurchdata.co.uk

 

[BABSBINI]

Hi Geoff,
Thanx for the input, but I think I should clarify that the whole application works great when its being accessed over a local network. Records do not duplicate, all users see the entries added/modified by other users and timer control kicks in to refresh the screen as its supposed to on local network. Its only when its on Citrix that it gives these problems. This, I think eliminates any coding issues, UNLESS anything has to be done differently if the application is running over virtual shared networks like Citrix.
Any more tips?
Thanx
Bini

 

[alvechurchdata]

I'm afraid that I can't think of anything. We've not used Citrix but we've had no issues with timers on Windows Terminal Server.

Can you add something on the form to prove that the timer is indeed running - perhaps show and hide an icon as the timer fires.

If the timer is running then it sounds as though there might be some issue with data being cached by A instead of being written to disk where C can read it and refresh the screen.

Geoff Franklin

http://www.alvechurchdata.co.uk