![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hello; MS Access 2000/Sql Server backend. We have a situation where an automated (access app -- based off of cmd button) append to a certain sql server table (from an ms access table) ceased to work. Our ERP System was upgraded along with changes applied to the database(probably new restrictions introduced). This append is unique because it appends an ole field. Our staff has to manually intervene daily now because this append doesn't work. What I did was (in our test db) look at the table in question in Enterprise and manually build a duplicate of it (with a slightly diff name). I was able to append to this copy structure no problem. The message that displays when the append is attempted (to the actual) refers to a trigger. After the results of my analyses and testing, I would say this message is accurate. Is it possible to use the ALTER TABLE table name DISABLETRIGGER type functionality right in the access module? With the append command in between the disable and enable? I typed it in just see how it accepted the syntax and I got errors. You would have to send it via a passthrough query, or use VBA and ADO to |
![]() |
| Thread Tools | |
| Display Modes | |
| |