> 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.

VNC will require a dedicated machine per remote user, but Terminal
Services works well (for most things). We have found that it is faster
to remote desktop into our data centre and use our application on a
high spec server than to use it locally over a reasonable speed ADSL.
Speedwise, rdp/ts is much faster than TightVNC. I have on more than
one occasion forgotten I was not working on my local machine and
started looking for the Firefox icon before coming to my senses. It is
usable on 56K, probably want 256K or better connection to live with it
though as a more permanent solution. Printing to a local printer can
be a bit of fun if you don't buy a third party tool like Thinprint.

Of course it will not allow the user to work while the connection is
down, but providing the timeouts are sufficient they could resume
where they left off without issue.

Adam