On Wed, January 3, 2007 2:03 pm, Adam wrote:

> But what you have (and I don't mean to be rude) is a bit of a design
> limitation. Client-server doesn't work well over an unreliable
> connection, and WANs always have and always will be unreliable. One of
> two things may happen. Either you tell the customer that your
> application requires a reliable network connection and they will get
> these sorts of errors if it ever becomes unreliable, or you need to
> design your application to expect this sort of thing to happen, using
> something like a RemObjects service on the server and having your
> client connect to that service (which in turn makes a connection,
> performs whatever task then closes the connection or returns it to a
> pool or something).
>
> Hope that helps
>
> Adam
>

Since the application is on windows, he might consider using remote
desktop, terminal services, or vnc(I recommend tightvnc on windows). I've
had tons of reliability problems with different types of applications on
unreliable connections. I've always found the solution to be easy, so slap
the application on a server and have the user connect to the server if
reliability is needed.

Tsume