 | |
key violations when there are no key violations
comp.databases.ms-access comp.databases.ms-access
 |
| | Thread Tools | Display Modes |
#11
 
| |||
| |||
|
Re: key violations when there are no key violations -
03-29-2011
, 09:33 AM
|
On Mar 29, 9:48 am, "Bob Barrows" <reb01... (AT) NOyahooSPAM (DOT) com> wrote: Tony_E wrote: On Mar 29, 8:52 am, "Bob Barrows" <reb01... (AT) NOyahooSPAM (DOT) com> wrote: Tony_E wrote: On Mar 29, 8:21 am, Tony_E <bluestealt... (AT) hotmail (DOT) com> wrote: Hello; I made a mistake in my previous explanation--what I meant was that I checked the master table, examined a certain record, and attempted to add record to the child table-using the value that already exists in the master table. I got the same message Ok, I got passed that primary key foreign key obstacle--these tables have a one to one relationship -- I have to add a record to the parent table before adding a record to the child table. So when I attempted to add a record to the parent table I received a Failure message referencing a TRIGGER. "Insert in linked table "CUSTOMER_ORDER" failed. Error in trigger INSERT_CUSTOMER_ORDER. Is there anything I can do now to insert to this table? Ask the database designer or dba? I hesitate to suggest disabling the trigger without knowing what business rule it is enforcing Yes I think when the append functionality is run, the trigger will have to be disabled. In one of my other posts you indicated that to disable I would have to use a passthrough query or VBA and ADO. Could you give me a sample of how to do it in a passthrough? It's not hard to find via google so OK ... I'm just very hesitant here - do you have any idea what that trigger is actually doing and what the consequences of bypassing its functionality will be? Before going down this road you should at least figure that out - you haven't provided the version of your sql server so it's hard to get into specifics here. Run this search to find out how to display the text of the trigger so you can see what it's for:http://www.google.com/search?sourcei...=SQL+Server+tr... Then, after you are satisfied that disabling the trigger is safe, run this search to see how to do it in your version of sql server:http://www.google.com/search?hl=en&s...rver+trigger+d |
Quote:
|
If you do disable it, you should consider performing its functionality yourself just to make sure whatever rules it is enforcing are not violated.- Hide quoted text - - Show quoted text - I don't know what version of sql server we use because I don't have access to SQL Enterprise or Qry Analyzer. I will definitely have a conversation with my manager before even testing disable functionality on our test db. Thanks for the link. |
SELECT @@VERSION
in a passthrough query
#12
| |||
| |||
|
|
Tony_E wrote: On Mar 29, 9:48 am, "Bob Barrows" <reb01... (AT) NOyahooSPAM (DOT) com> wrote: Tony_E wrote: On Mar 29, 8:52 am, "Bob Barrows" <reb01... (AT) NOyahooSPAM (DOT) com> wrote: Tony_E wrote: On Mar 29, 8:21 am, Tony_E <bluestealt... (AT) hotmail (DOT) com> wrote: Hello; I made a mistake in my previous explanation--what I meant was that I checked the master table, examined a certain record, and attempted to add record to the child table-using the value that already exists in the master table. I got the same message Ok, I got passed that primary key foreign key obstacle--these tables have a one to one relationship -- I have to add a record to the parent table before adding a record to the child table. So when I attempted to add a record to the parent table I received a Failure message referencing a TRIGGER. "Insert in linked table "CUSTOMER_ORDER" failed. Error in trigger INSERT_CUSTOMER_ORDER. Is there anything I can do now to insert to this table? Ask the database designer or dba? I hesitate to suggest disabling the trigger without knowing what business rule it is enforcing Yes I think when the append functionality is run, the trigger will have to be disabled. In one of my other posts you indicated that to disable I would have to use a passthrough query or VBA and ADO. Could you give me a sample of how to do it in a passthrough? It's not hard to find via google so OK ... I'm just very hesitant here - do you have any idea what that trigger is actually doing and what the consequences of bypassing its functionality will be? Before going down this road you should at least figure that out - you haven't provided the version of your sql server so it's hard to get into specifics here. Run this search to find out how to display the text of the trigger so you can see what it's for:http://www.google.com/search?sourcei...=SQL+Server+tr... Then, after you are satisfied that disabling the trigger is safe, run this search to see how to do it in your version of sql server:http://www.google.com/search?hl=en&s...rver+trigger+d ... If you do disable it, you should consider performing its functionality yourself just to make sure whatever rules it is enforcing are not violated.- Hide quoted text - - Show quoted text - I don't know what version of sql server we use because I don't have access to SQL Enterprise or Qry Analyzer. I will definitely have a conversation with my manager before even testing disable functionality on our test db. Thanks for the link. You can discover the version by running SELECT @@VERSION in a passthrough query- Hide quoted text - - Show quoted text - |
#13
| |||
| |||
|
|
On Mar 29, 10:33*am, "Bob Barrows" <reb01... (AT) NOyahooSPAM (DOT) com> wrote: Tony_E wrote: On Mar 29, 9:48 am, "Bob Barrows" <reb01... (AT) NOyahooSPAM (DOT) com> wrote: Tony_E wrote: On Mar 29, 8:52 am, "Bob Barrows" <reb01... (AT) NOyahooSPAM (DOT) com> wrote: Tony_E wrote: On Mar 29, 8:21 am, Tony_E <bluestealt... (AT) hotmail (DOT) com> wrote: Hello; I made a mistake in my previous explanation--what I meant was that I checked the master table, examined a certain record, and attempted to add record to the child table-using the value that already exists in the master table. I got the same message Ok, I got passed that primary key foreign key obstacle--these tables have a one to one relationship -- I have to add a record to the parent table before adding a record to the child table. So when I attempted to add a record to the parent table I received a Failure message referencing a TRIGGER. "Insert in linked table "CUSTOMER_ORDER" failed. Error in trigger INSERT_CUSTOMER_ORDER. Is there anything I can do now to insert to this table? Ask the database designer or dba? I hesitate to suggest disabling the trigger without knowing what business rule it is enforcing Yes I think when the append functionality is run, the trigger will have to be disabled. In one of my other posts you indicated that to disable I would have to use a passthrough query or VBA and ADO. Could you give me a sample of how to do it in a passthrough? It's not hard to find via google so OK ... I'm just very hesitant here - do you have any idea what that trigger is actually doing and what the consequences of bypassing its functionality will be? Before going down this road you should at least figure that out - you haven't provided the version of your sql server so it's hard to get into specifics here. Run this search to find out how to display the text of the trigger so you can see what it's for:http://www.google.com/search?sourcei...=SQL+Server+tr... Then, after you are satisfied that disabling the trigger is safe, run this search to see how to do it in your version of sql server:http://www.google.com/search?hl=en&s...rver+trigger+d ... If you do disable it, you should consider performing its functionality yourself just to make sure whatever rules it is enforcing are not violated.- Hide quoted text - - Show quoted text - I don't know what version of sql server we use because I don't have access to SQL Enterprise or Qry Analyzer. I will definitely have a conversation with my manager before even testing disable functionality on our test db. Thanks for the link. You can discover the version by running SELECT @@VERSION in a passthrough query- Hide quoted text - - Show quoted text - Microsoft SQL Server *2000 - 8.00.2039- Hide quoted text - - Show quoted text - |
I have all the appends working now. It didn't need any disabling, just
a logical approach on my part. The records that are supposed to be
appending are appending. One of the fields that are appended are from
text to OLE. The data in the text field does not show up in the OLE
field after the append. Any ideas why it would not display?
#14
| |||
| |||
|
|
Hello; I have all the appends working now. It didn't need any disabling, just a logical approach on my part. The records that are supposed to be appending are appending. One of the fields that are appended are from text to OLE. The data in the text field does not show up in the OLE field after the append. Any ideas why it would not display? |
mean "binary" or "varbinary"? Are you calling it "OLE" because that is what
Access calls it when you view the linked table's Design View?
Why would you store character (text) data in such a field?
I have never dealt with OLE fields, so I think I'm going to bow out of this
one now. Hopefully someone who has will jump in.
#15
| |||
| |||
|
|
Tony_E wrote: Hello; I have all the appends working now. It didn't need any disabling, just a logical approach on my part. The records that are supposed to be appending are appending. *One of the fields that are appended are from text to OLE. *The data in the text field does not show up in the OLE field after the append. * Any ideas why it would not display? I'm *a bit confused: SQL Server does not have an OLE datatype. I suppose you mean "binary" or "varbinary"? Are you calling it "OLE" because that is what Access calls it when you view the linked table's Design View? Why would you store character (text) data in such a field? I have never dealt with OLE fields, so I think I'm going to bow out of this one now. Hopefully someone who has will jump in. |
the data type of the field that displays in a "specs" window in the
ERP app we use. Again thanks so much.
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.