>>Just a quick question for those of us who are Internet challenged. In VFP 6.0 SP3 we have the _VFP.ThreadID property. Do you have any idea why this value doesn't match that which GetCurrentThread() returns. GetCurrentThreadID() returns the same value, but as I understand it, GetCurrentThread() returns a pseudo-handle to the thread. I guess what I'm asking is why would the pseudo-handle work where the real one wouldn't?
>
>The Thread ID is kind of like the ProcessID - it's something you can use to
>retrieve a real handle to the thread. The ID is something you'll see in
>a debugger and something you can store with your application. The handle
>is the actual physical aspect that controls the thread or process.
>
>IDs are sequentially numbered and easy to read. Handles are large numbers
>that the system generates uniquely.
>
>Standard Windows API fare I guess...

Just to amplify things, a process or thread id is global - it is valid regardless of the process running. The process handle and thread handle are local to the process holding the handle - it's not valid outside the process that gets it.

>
>+++ Rick ---