>Hi,
>
>>>>Thinking some more about what you want to, ASSERTs are the way to go. They're designed specifically for developer errors.
>>>
>>>In COM objects ?
>>
>>You can still instantiate them within Fox as ordinary objects while developing. Then it'd surely work. After that, it's runtime - and runtime simply ignores assert, set step, debug, suspend (did I forget any?).
>
>But the question was about trapping bad parameters when the COM object was used by other developers. Assert wouldn't work then.....

Um, in that scenario, right. It goes into the dark woods of COM debugging... or the darker wood of thoroughly documenting what we give to others :).