Other than that I think the RDP does mess with Windows eventing a bit and it's possible that VFP is having problems with this when using timers. This might affect file based apps but shouldn't affect COM based apps.
+++ Rick ---
from Maui, Hawaii
Other than that I think the RDP does mess with Windows eventing a bit and it's possible that VFP is having problems with this when using timers. This might affect file based apps but shouldn't affect COM based apps.
+++ Rick ---
I work on a site on a daily basis that has a two different web connection processes (handled with different script maps) and a couple of async process servers that handle longer running processes such as pdf file generation, generating word documents etc.
What is unusual is that almost everytime I log in, one of the process will hang. Since I generally run 3 web connect servers, having one of them hang wasn't that big of a deal. I thought there was something in my code that caused the process to hang and I put some debugging info that tracked every request and I found that the process that would hang did so usually at the time I logged in and not at some time previous.
When the process hangs, the window usually goes blank, I can't activate the window and if the exit button is visible, it does not respond. So task manager is the only way to kill the process. Yesterday it was one of my async processes that looked like it was ready to process but it wasn't responding, and records were building up in the database.
Killing it and starting the process over again had it working fine.
I think maybe a timer goes funny when remote desktop starts, but who knows, I can't see exactly what is happening.
It is more of a nuisance than anything. I can easily see which web process has hung up when I log in, but the async processes are little sneakier. But I just have to be sure to kill them and then restart them again.
Anyway, I am curious to know if anyone else has experienced this.
Bob