ROFL!!!! That's correct, we should. <g>
>>>You cannot instantiate the control directly. It will work fine in development, but will error out, even if it's properly installed.
>>
>>The problem has to do with a licensing issue. Drop the ActiveX control on a form, and use it to instantiate the class. This has a side benefit of allowing you to control the position of the dialog, since it's always relative to the form it's on.
>I found that out. I just didn't know it was a licensing issue as the crappy error message says something about insufficient memory. So I did drop it onto a form a few days ago and all is well.
>I guess we should all learn from MS ActiveX developers on how to do proper >error messages. I think I should start saying that to my users. When an error >occurs they'll get a random message:
>"Insufficient memory for this operation"
>"Problem found between chair and keyboard"
>"Program failure: improperly placed widget"
>"Program failure: not enough money sent to the developer. Send some more."
