error "Input line too long" from 4GL 7.32UC1

I have a piece of 4GL code, which was originally built by 4GL 7.30UC1. After upgrade to 4GL 7.32UC1, I got the following error: c4gl -a -e foo.4gl i4glc2: file "foo.4ec", line 50044: Input line too long i4glc2: file "foo.4ec", line 50044: Invalid character ''(0xfffffffe)' at column 0 I have checked the foo.4ec, it is caused by a very long query. In the 4ec built by 7.30 UC1, this query keeps the origianl line arrangment. However, in the 4ec generated by 7.32 UC1, the whole query becomes one line. I am wondering besides I break this query into several quries, is there a way to work around this problem? Thanks a lot! Yan

hantao wrote: > I have a piece of 4GL code, which was originally built by 4GL 7.30UC1. > After upgrade to 4GL 7.32UC1, I got the following error: > > c4gl -a -e foo.4gl > i4glc2: file "foo.4ec", line 50044: Input line too long > i4glc2: file "foo.4ec", line 50044: Invalid character ''(0xfffffffe)' > at column 0 > > I have checked the foo.4ec, it is caused by a very long query. > In the 4ec built by 7.30 UC1, this query keeps the origianl line > arrangment. However, in the 4ec generated by 7.32 UC1, the whole query > becomes one line. > > I am wondering besides I break this query into several quries, is > there a way to work around this problem? > > Thanks a lot! > Yan Patch. If it is what I'm thinking it's a BUG and it doesn't need a particulary long query. Some magic number of ANDs/ORs may cause this. If it's on Solaris and I remember correctly 7.32UC1X1 will do the trick. Contact your support service. Regards.