Right, I see what you mean. I was just working on a class that had a property that has to be a number between 0 and 255. The assert checks it being entered incorrectly at design time and the assign handles it at runtime.

Thanks.

>Yes, you can use asserts exactly like that. In my case it's not really as much a "design time" error as it is a safety valve.
>
>>Right, I thought asserts in that case would be better. In your expample you could just:
>>
>>ASSERT RIGHT(This.MyValue, 1) == '\' ;
>> MESSAGE 'Property MyValue must contain the trailing backslash'
>>
>>In the class init. Now it runs when you are developing and you can turn it off when you compile the finished app.
>>
>>Or am I misunderstanding how asserts are used?