Was new to me after 25a. :)

Why would you EVAL()? ("blabla") and (blabla) are expected to be literal string so =[("blabla")] and ="(blabla)" should do.

Update:
=' ("blabla")' rather then =[("blabla")], I don't trust [] as string delimiter since it's #DEFINE behaviour.

>Think this is a know issue
>
>solve like
>

>=eval(["blabla")]
>"(blabla)"
>

>
>>FYI
>>
>>Try the following:
>>- Create a vcx based class
>>- add two properties (or use any that is char)
>>- into the first put a string like ("blabla")
>>- into the second put a string like (blabla) (note: no number, no function)
>>- close the class
>>- reopen the class check the error - and the values
>>
>>Reason:
>>The VCX stores an expression value of property like myprop : =" A value" as myprop = (" A value") within the VCX (properties field)
>>The values from above get stored without testing for the syntax, but opening the the class does check for some syntax.
>>
>>I have a little fun on FoxBin2Prg ...
>>(－‸ლ)