>>>>And I am still not comfortable even reading the registry. I would rather one or two new customers get the ugly error message. Once they register the ActiveX (which is done via a nice Setup), the error will not occur.
>>>>
>>>
>>>
>>>Reading the Registry is easy. There's a class in the FFC for it. Here's an article I wrote about it:
>>>
>>>
http://www.tomorrowssolutionsllc.com/Articles/Working%20with%20the%20Registry.pdf>>>
>>>Tamar
>>
>>Thank you for the article. As I mentioned that it is not simply reading the registry that concerns me. But if my code reads the wrong key or registry and determines that the ActiveX is not registered, the customer will get a false error message. This, IMHO, could create more support issues than the ugly error message the customer gets when the ActiveX is not registered.
>
>Once you figure out what key you're looking, why would you ever read the wrong key? This is like anything else; it's a matter of figuring out what you need and writing the code.
>
>Tamar
I will see first if I can implement what Dragan suggested. It would be better solution, IMHO. Thanks.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
