Andy..
22nd March 2011, 18:53
Just made some changes to a report and now it won't compile with error:

rtdsls9441110002:
repgen '2tdB40Oc4wstnsls944111000' -c 'tdB40Oc4wstn' -o "d:\baan\tmp\tmp0085295
90" -qe "d:\baan\tmp\tmp008529591" -x "d:/baan/tmp/tmp008529592"
bic "d:\baan\tmp\tmp008529590" -d ottstprepdll -u -o rtdsls9441110002 -f "d:\ba
an\tmp\tmp008529589" -qe "d:\baan\tmp\tmp008529591"
tmp008529590( 366): Error: Enumerate/Bitset expression expected.
1 ERROR REPORTED.

2 questions...
1. what does this error mean?!
2. is there a way to retain these report tmpfiles that are immediately deleted? Maybe that would give a clue of what's happening?

Tried it on 2 different servers with old and new porting and toolsets and get the same error. Tried to remove ALL the report script and this error is still top of the list so I assume its something to do with layouts but I have barely changed anything in there since the last OK compile (but have changed a lot since the last backup) :(

tomlbacon
22nd March 2011, 19:07
Display the line 366 that has the error so can see it.

Andy..
22nd March 2011, 20:09
the report script only goes to line 124 and as it says above even if I delete all the report script I still get the same error (as well as some more obviously due to missing script). The report is in line 366 of the tempfile which is immediately deleted during compilation

tomlbacon
22nd March 2011, 20:28
Look at the Program Script not the Report Script for line 366.

Andy..
22nd March 2011, 22:28
line 366 of the source is the first line below:

if isspace(itm.dsca) then
select tiitm001.dsca
from tiitm001
where tiitm001._index1 = {:tdsls940.sitm}
selectdo
itm.dsca = temp.arr(1,1)
selectempty
item.desc = ""
itm.dsca = ""
endselect
endif

this line hasnt been changed since the report last compiled without error though :(

mark_h
23rd March 2011, 16:09
This looks to be in the report - not the session. Have you backed out your changes and recompliled? What about restoring the original session - have you tried that? If you can get back to the original report - then you can make your changes again. One at a time of course to see which one gives this error.