I am getting the following fatal error:

Process 91 - Degree Mismatch in reference predicate (tdltc001)

Error 301 (query not correct) on select.

what is meant by the "Degree Mismatch in reference predicate (tdltc001)" ??

same session runs error free on another server.

Nick,

I am guessing there is a difference in the porting set between the 2 servers. BaaN has released a New Query Processor which has some changes with the SQL statements.

301 ESQLQUERY
This indicates a general SQL error. It occurs when the SQL query is syntactically incorrect.

302 ESQLSYNTAX
This indicates that the SQL syntax is not correct.

By any chance do you have a "refers to" in the select?

Not sure if this is the error message I got, but with a new porting set the refers to has to go in to correct direction. Previous porting set didn't seem to care.

Debbie

yes the Baan instance where the error occurs has a new porting set. Hopefully the Baan standard session code is not the culprit and the problem lies in the customized report.....thanks for the help.

more problems and worse.

The fatal error occurs within the standard session (standard code not customized). Also another problem is now I cannot compile the customized report see errors below. I am on port set 6.1c.06.04 where the older port set is 6.1c.04.01

function print.lot.data()
{
line = 2
select tdilc401.*, tdltc001.*
from tdilc401, tdltc001
where tdilc401._index1 = {tdilc.koob.act.rpl, :tdrpl100.orno,
:tdrpl100.pono, :tdrpl100.srnb}
and tdilc401.proc = tcyesno.yes
and tdilc401.item = :tdrpl100.item
and tdilc401.cntr = :tdrpl100.cntr
and {tdilc401.cprj, tdilc401.item, tdilc401.clot} refers to tdltc001
order by tdilc401.koor, tdilc401.orno, tdilc401.pono, tdilc401.sera, tdilc401.serb
selectdo
print.report()
endselect
}



Report Compile errors: (a large list of these but with different TSS characters)

(ISO-8859-1) Error in TSSwc_width:
can't convert TSS character 0x9b29a57e

yes, this problem is due to the new porting set.

try revising your function print.lot.data() to

{tdilc401.cprj, tdilc401.item, tdilc401.cntr,tdilc401.clot} refers to tdltc001

this new porting set checks your "refers to" statement which in your case is the index1 of your tdltc001 table.

i had this problem before and for standard scripts i just upgraded the objects to the latest version (post new porting set). you should be fine.

I cannot change the standard selects, and I cannot install new objects as I am on an old b2 version as the solution dependencies will cause problems.....looks like port set 6.1c.06.06 has a fix for the problem.