DDQING
8th November 2002, 10:08
hi,
when i run posting integration transactions (session tfgld4201m000),a bw error appear"error 206,record is no locked on tfgld417101 in up_data(51)".so i cant post transaction.who know how to solve it?
Carmar
11th November 2002, 09:06
Hi,
The specified table <table-name> is not in the database.
The database server cannot find a table or view specified in the statement. The table or view might have been renamed or dropped from the database.
Check the names of tables and views in the statement. If the names are spelled as you intended, check that you are using the database you want. To find the names of all tables in the database, query the systables table. To find the names of all views, query the sysviews table.
Regards, Carmar
EdwinvdBorg
12th November 2002, 01:36
Hi DDQING,
An error 206 is in 99.99% of the cases a programming error in BAAN that can only be solved by BAAN Support.
Please contact them immediately unless the problem is caused by a customization.
Regards,
Edwin
OmeLuuk
12th November 2002, 14:16
Carmar: The specified table <table-name> is not in the database. This is error 506.
I think Edwin is right, but I cannot imagine that that error still exists in the standard software... an error like this would not exist for a long time.
Normally in an SQL statement you need to select with a (delayed) lock when you intend to modify a record ("... for update") before a db.insert / db.update command. The error indicates that the selection is not done ... for update.
Run a ttstpsessinfo on your session to see what your current version is and whether or not you run standard software. And if you feel not capable in handling this: log a case.
EdwinvdBorg
14th November 2002, 23:44
Hi OmeLuuk,
When it comes to BAAN software never say never again!
Eventhough one might expect the standard software has been stabilized enough by now. However, in real life we still deal with solutions provided by BAAN Support and those can cause unforeseen problems.
Regards,
Edwin
OmeLuuk
15th November 2002, 10:00
I did not say that the error cannot be (re)introduced in the software, but if it is, I daresay it will not sit there for a long time, not this error in this session.
Every programmer hates a badfix, especially his own.