Sounds like a nice little hack. I remember having to do things like that to GENSCRNX also.

>>I sort of remember the same problem, although it's been a while since I worked in FPW2.6. I think in your case the thing to do would be to create a cursor with the calculated values first and put that in the browse instead.
>>
>>>I have a project that I'm doing in FPW2.6 (Intermediate step between DOS version and total rewrite in VFP/VB/VJ++). I am attempting to use the inbrowse driver for genscrnx but I'm running into a problem.
>>>
>>> I have a field which is calculated (sort of) based upon certain criteria. What ends up happening is that a text string is built based upon several fields and placed into a single field of the browse. The problem is that the code to build that string is too long for the inbrowse driver. I have changed the set memowidth value with no affect (set to 400). The line of code is greater that 254 characters.
>>>
>>>*:BROWSEFIELDS B="("+vsarate+") "+IIF(jumpprice=99.99,"","Jump: "+STR(jumpprice,5,2)+" ")+IIF(flatprice=99.99,"","Flat: "+STR(flatprice,5,2)+" ")+IIF(ggasprice=99.99," ","Gas: "+STR(ggasprice,5,2)+"")+IIF(airprice=99.99," ","AIR: "+STR(airprice,5,2)):H="SA":50
>>>
>>>I have tried to break the line up (place on several line each starting with *:BROWSEFIELDS) but I get the "missing operand" or "Syntax" error.
>>>
>>> Has anyone seen/overcome this problem?
>>>
>>> Is it just me?
>
>
>What I ended up doing is to add *; to the end of the line that is too long to signify it is continued on the next line. In INBROWSE.prg I changed the code to test for the *; at the end of the line. If it is there, the code to add the comma and line feed is skiped and the *; are removed from the line before it is added to c_return variable string.