BaaN works fine but I see this error and I don't know what table creates the problem.

In log.informix :

******* S T A R T of Error message *******
Log message called from /view/port.6.1c.07.06/vobs/tt/servers/INFORMIX_1/inf_error.c: #385 keyword: FETCH_CURSOR
Pid 700208 Uid 103 Euid 103 Gid 101 Egid 101
user_type S language 2 user_name ze01 tty ote locale ISO88592/NULL
Errno 0 bdb_errno 0
Log_mesg: Code -403 ISAM err 0 #rows 0 Lrow 3338754 Offset 80
******* E N D of Error message *******

******* S T A R T of Error message *******
Log message called from /view/port.6.1c.07.06/vobs/tt/servers/INFORMIX_1/inf_error.c: #393 keyword: INFORMIX_ERROR_MESSAGE
Pid 700208 Uid 103 Euid 103 Gid 101 Egid 101
user_type S language 2 user_name ze01 tty ote locale ISO88592/NULL
Errno 0 bdb_errno 0
Log_mesg: The size of a received row disagrees with the expected size.
******* E N D of Error message *******
Someone an idea how to solve this?

Have you considered trying to generate a dbs.log?
Do you know what the user was running at the time the error message occured?

Was a change made to the data dictionary recently?

-------------
Jason Foster

http://jasonfoster.emurse.com

I've used -- -set DBSLOG=0307777 but no entry in the log file.
It happens to every user using that company.
To trigger the error I just open "maintain paper" (no error), then "maintain fonts by paper type" (error generated). Another combination of 2 tools sessions gives the same result.
Yes, it started after changing the data dictionary.
A company in the same package combination, but created after the data dcitionary was changed, doesn't have this problem.
((Normal users don't use tools sessions, but they also generate this error. So I think it must be tools AND company related))

Try 1570 instead of 7777.

What are the session numbers that are being affected?

While normal users don't use the tools sessions themselves, Baan would definitely reference tools tables in order to generate reports.

Once the table is identified then you can create runtime dd and reconfig. It appears that the runtime dd is out of sync with the database for the existing company which might indicate that reconfig was not run after the dd was changed. However, new companies would pick up the changed dd.

----------------------------
Jason Foster

http://jasonfoster.emurse.com/

1570 does the job. The problem table is ntwrd030.
Since we don't need package nt, I've deleted it and started rebuilding DD.
Hopes this helps.

removing it and rebuilding did the job.

Thanks for helping me.