Re: Using Passthrough Query to Disable Triggers
- From: "jeff" <jeff@work>
- Date: Mon, 4 Aug 2008 10:58:44 +0800
DOH
I AM an idiot..... got it going.. i had my table name wrong AND was
prefixing the SQL with PL/SQL: ... what am i? an idiot.. thx Stefan...
"jeff" <jeff@work> wrote in message
news:OO8w$yd9IHA.3612@xxxxxxxxxxxxxxxxxxxxxxx
stefan
thx for your post, how do i run this from an MSACCESS pass through query?
My previous Passthrough Query used the following for MSSQL:-
EXECUTE sp_msforeachtable "ALTER TABLE tablename DISABLE TRIGGER ALL"
I cannot get this to work in the MSAccess pass through query...
PL/SQL: ALTER TABLE tableName DISABLE ALL TRIGGERS;
I get an "..Invalid SQL statement.." error
cheers
Jeff
"Stefan Hoffmann" <stefan.hoffmann@xxxxxxxxxx> wrote in message
news:%23yQcU978IHA.1568@xxxxxxxxxxxxxxxxxxxxxxx
hi Jeff,
jeff wrote:
is there a way I can run a passthrough query to call an appropriatePL/SQL: ALTER TABLE tableName ENABLE|DISABLE ALL TRIGGERS;
Oracle Stored Procedure to do the same as MSSQL???
mfG
--> stefan <--
.
- Follow-Ups:
- Re: Using Passthrough Query to Disable Triggers
- From: Stefan Hoffmann
- Re: Using Passthrough Query to Disable Triggers
- References:
- Using Passthrough Query to Disable Triggers
- From: jeff
- Re: Using Passthrough Query to Disable Triggers
- From: Stefan Hoffmann
- Re: Using Passthrough Query to Disable Triggers
- From: jeff
- Using Passthrough Query to Disable Triggers
- Prev by Date: Re: Using Passthrough Query to Disable Triggers
- Next by Date: Re: Muliptiple Records
- Previous by thread: Re: Using Passthrough Query to Disable Triggers
- Next by thread: Re: Using Passthrough Query to Disable Triggers
- Index(es):
Relevant Pages
|