I'm pretty new at dealing with FoxPro, and my users are having a
problem running an old FoxPro (5.0) application thru Citrix. It seems
that, every once in a while, they will go into a memo field to make
changes and their Citrix connection will be lost. This only occurs
randomly, so I am at a loss as to the cause.

the only code in this part of the program is as follows:

modify memo {fieldname}


is there any known conflict between FoxPro and Citrix that may be
causing this and that there may be a workaround for?

Thanks for any help you can provide.

when the connection is "lost" what happens? is the session terminated?

there *IS* a problem with corruption (on any system) if you have data "being
edited" and you suddenly terminate the application.

If a connection is "lost" the session should remain active until they reconnect
and all would be fine. as far as the terminal server session is concerned,
they're still running th app.

However, if you have it configured to "end session" on disconnect; you'll have
problems, and need to code for this bad behaviour.

On 17 Feb 2004 08:51:35 -0800, michael_bennett9 (AT) hotmail (DOT) com (Michael Bennett,
MCSD) wrote:


---
Remove x's to send.

following up; approaching end of life for me; we have a "ts helper" library for
vfp - with it; combined with a timer etc; you can 'sense' the user has
disconnected and close tables, etc quit the app & end session....


On 17 Feb 2004 08:51:35 -0800, michael_bennett9 (AT) hotmail (DOT) com (Michael Bennett,
MCSD) wrote:


---
Remove x's to send.

Sorry for my delayed response. The news server I use doesn't update
very often.

when the connection is "lost" the session terminates. The good thing
is, no data problems are happening. The bad thing is that every time
this happens, we have to go to the Citrix server and delete and re-add
the profile for the user that got blown out.

It appears that the connection gets blown out almost as if it were
properly exited, from what I can tell.

We tried reconfiguring the Citrix sessions so they would stay open and
the user could reconnect as if nothing happened, but this did not
help. Reading over the Citrix documentation, everything seems to be
configured and optimized properly.

Not a huge problem, just a VERY annoying problem for users and
programmers alike.