>>Done. And from one "nitpicky programmer" to another thanks. You're the first one to spot that typo (and the last< g >).
>
>I had a feeling you might be the same way. :)

If you read the article on the Advisor site, imagine how I feel about what happened to my indentation.< g >

>I read your article and I thought it was put together very well. It looks like it will work great.

Thank you, but a lot of the credit (for the composition) must be given to Tamar Granor. She's very nice to work with and makes me sound a lot more literate than I actually am.

>Since you like poling around in Win32 I have another question for you. I need to implement some kind of user licensing for my software. Do you know of any way to limit the number of people who can run a FoxPro program? The software is installed on a server of some type (usually NT) and network users run the program.

I don't recall ever seeing anything in the API that would be able to do this. Of course, there's so much to it, that the functionality could be there. If it is, Ed Rauh might know. I, frankly, don't. Additionally, the solutions that I've seen from time to time haven't utilized any API stuff. I seem to recall this subject being discussed here some time back, but I can't give you any particulars.

>The problem is that it has to be absolutely crash proof, or we'll generate a lot of tech support calls. If someone's system locks up and they reboot I need to make sure their license gets added back to the pool of free licenses.

Understand completely. Can't have a user just turn off the machine, without somehow having the available licenses properly accounted for. Same thing with GPFs and (everybody's favorite, the good old) BSD. As a corporate developer, I've never had to try and resolve this problem, so I'm not a good source for a solution. Hopefully, someone who has dealt with it will jump in and at least get you started in the right direction.