noonie
23rd September 2003, 18:12
I'm trying to attach an insert trigger to tiitm001, to write to an item# and current date to an separate audit table. The update trigger works fine, however I get the following after the insert fires :
Fatal error: Error 1000 (bdb_errno 520) on tiitm100100 in SELECT
Fatal error : Can no continue in tiit,0202s000 in DLL : otiitmd110003 (get.company)
Any suggestions? thx.
vahdani
23rd September 2003, 21:41
I must admit SQLServer triggers are not my speciality but I have programmed some Oracle PLSQL triggers on Baan Tables in my time. In any case can you please post the script of your trigger? This would definitely help :)
noonie
24th September 2003, 15:10
Double post
noonie
24th September 2003, 15:15
Thanks for the attempt Vahdani!
It's pretty basic :
Create Trigger RecordModDate On ttiitm001100
For Update, Insert
As
Insert Into ItemModHist
Select t_item, getdate()
From INSERTED
It works fine if I make it solely an update trigger. I tried setting up 2 separate triggers, one for update, one for insert, and crossed my fingers.....same results.
dave_23
25th September 2003, 03:20
Hi Noonie,
If I were to ASSUME that you're using the Level 1 SQL driver....
Which means that every time you insert data into your table outside of Baan it will corrupt the table....
search the board for "hash columns" or Level 1 driver...
If that's not the case, let us know! thanks!
Dave
noonie
30th September 2003, 18:38
I think I'm using Level2. I didn't see any real clear cut way of determining that on any of the posts.
I upgraded to MSSQL2000 about a year ago. There was a section in the upgrade quide that listed copies of the db_resource file, and what they should look like for each of the 2 driver versions.
I noticed it had a line I was missing:
msql_level1:0
(I also happened to notice that this section of document U7648AUS has been removed since I printed it about a year ago)
I added this line...same results. I also installed the latest porting set...same results.
I'm still screwing around with things to try and get it working.
Thanks for pointing me in the right direction!
EdHubbard
30th September 2003, 23:30
I think you will be on level 1 driver as Baan did not and will not create a level 2 driver for Baan 4 on SQL Server 2000 (or SQL Server 7). This is despite many documents suggesting that there would be.
I don't think you can use triggers therefore I am afraid.
If you discover differently in the future or come up with an alternative, please post it here as I would be really interested to know.
good luck
Ed
noonie
1st October 2003, 21:02
Unfortunately, Ed is correct.
Here's Baan's answer to my question on whether or not they do or will exist for IVc4 :
For the moment we do not have an specific date or plans: Baan IV : _________ For the moment Baan has not plans to deliver a level 2 driver for SQL Server 2000 and switching to level 2 mode using porting set 6.1c.06.06 Baan or onwards will not work. db_resource file examples for Level 2 shown in document :
U7648A US BAAN IV/BaanERP SQL Server 2000 Upgrade Guide for BAAN IV and BaanERP are only relevant for iBaanERP. Reference to level 2 mode in document :
U7210B US Baan IVc Installation Guide for Microsoft SQL Server Version 2000 is not relevant.
iBaanERP 5.0b (Grieg) and 5.0c (Corelli):
Level 2 mode is fully supported from porting set 7.1d and onwards using SQL Server 2000 and onwards.
Back to the drawing board.