>>>> So, either way, there is a bug here. The only practical solution at this
>>>> stage will be to alter the ReportBuilder.App so that it checks for
>>>> expressions that are >255 characters in length, and doesn't allow
>>>> them. I will put in an enhancement request for SP2 for this on your
>>>> behalf.
>>>
>>> Wouldn't it be an ever better solution to remove the 255 characters limit?
>>
>>Possibly. I know which ER is more likely to be accepted though, as should everyone here who has been paying attention.
>
>You know more about the internals of VFP than I know, but I have seen many cases where it has been easier to remove a limit than creating workarounds.
?? It's impossible to "remove" a limit - there's ALWAYS a limit. I think you mean "increase" a limit.
Regards. Al
"Violence is the last refuge of the incompetent." -- Isaac Asimov
"Never let your sense of morals prevent you from doing what is right." -- Isaac Asimov
Neither a despot, nor a doormat, be
Every app wants to be a database app when it grows up
