>>>>>>I've come across this error recently in a web app using Web Connection. I've heard that AddProperty should never return this error and was unable to reproduce this myself. What I've found on the internet leads me to believe that this is a VFP 8 bug. Either SP1 for VFP8 or VFP9 will fix this error.
>>>>>>
>>>>>>Is this information correct?
>>>>>
>>>>>Are you able to get the exact command that produces this error?
>>>>
>>>>< object >.Addproperty( < name >, < variable > )
>>>>
>>>>Unfortunately, it is happening when I've setup with COM and the error only happens 1 in every 200 commands or so. I couldn't get that "Not a Character Expression" error to occur within command window. That's when I looked on the web and found a couple of articles that say this is an internal Foxpro bug.
>>>>
>>>>Try it yourself. The error doesn't make sense.
>>>
>>>Is it possible that < Name > is not a character at that time?
>>
>>I actually tried that and it gives the "Function argument type, value, or count is invalid."
>>
>>Here is a link to one of the threads I found.
>>
>>http://www.tek-tips.com/viewthread.cfm?qid=1183926&page=1
>
>Well, this thread convinces that it's VFP8 bug that does not occur in VFP9. Would it be hard for you to upgrade?

It's a cost. If our client is annoyed enough, we'll have to pay it.

I found another thread that suggests that the VFP 8 service pack will fix this bug as well. That would be the preferable route. Again, I am not certain of the validity of either of these threads.