Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums  General SQL Server Forums  New to SQL Server Programming  VB.NET trigger BUG!

Author  Topic  jcosta Starting Member 1 Post Posted - 2008-01-23 : 16:06:00 I have a very odd problem and I am at my wits end trying to figure it out. I am having an issues with a call logging application. The application version is EXACTLY the same from my dev box to their live environment. This involves two tables. The main table and the detail table. The application has two parts. During a save section 1 updates the main table and section 2 updates the details table. The insert happens in that order. Development Testing I have a dev box that is running Windows 2003 on Virtual PC. I VPN in to the client's network. They are running SQL 2005 and host the database for the client application I am running. I have the following VB.NET code attached to an assembly running on the SQL 2005 box in safe mode that fires a trigger on the details table for inserts and updates. <Microsoft.SqlServer.Server.SqlTrigger(name:="checkDetail", Target:="Detail", Event:="FOR INSERT, UPDATE")> _ Public Shared Sub checkDetail() Throw New Exception("test") End Sub I open the application on my development box. It connects using an odbc connection to the SQL Server over the vpn. I type in my info in section 1 and section 2 and hit the save button. It inserts a record into the main table and then upon insert of the record into the detail table it generates an error because of my trigger, which is what I expect it to do. Live Environment Now, I connect to their db server via remote desktop and log into the local box via an admin account. I open up the same application and perform the same steps but this time I get the error like I expect but the record into the main table is never inserted (or it is inserted and then immeditly deleted, which I suspect is happening). I perform exactly the same steps but using my dev box connecting to the same SQL 2005 server over vpn it inserts the record in step 1 but on their server it won’t insert the record. The ODBC drivers are the same version. I have no idea what is different but something is. I even ran filemon to see what files it is using to pass the data via odbc and I don't see files it is using that are different from machine to machine. Thanks for the help!