Re: Executing SQL Statements throught ADO

In article <lpMzb.9514$d35.2257_at_edtnps84>, mfilson29NOSPAM_at_hotmail.com says...
> Hi All,
>
> Here's the issue I'm having... I have a VB COM component that is used to
> parse SQL files and apply them to an instance of Oracle. Most of the
> statements in the sql file work but a few don't. Here is an example of an
> offending one:
>
>
> CREATE OR REPLACE TRIGGER TR_SEQ_APPLICATION_SETTINGS
> AFTER INSERT OR UPDATE ON APPLICATION_SETTINGS
> FOR EACH ROW
> BEGIN
> SELECT SEQ_APPLICATION_SETTINGS.nextval INTO :new.ID FROM dual;
> END TR_SEQ_APPLICATION_SETTINGS;
> /
>
>
> The Sequence that's referenced is created successfully and my code says that
> the trigger is created (ie, no errors are thrown), but when I attempt to
> insert a bunch of values into the table APPLICATION_SETTINGS, errors are
> generated. Is there something about the syntax of this create statement
> thats wrong. For what it's worth, the above statement can be run in SQL
> PLUS successfully and the trigger is created.
>
> Cheers.
>
>
>

If the provider is choking on :new, try adding the REFERENCES clause:

CREATE OR REPLACE TRIGGER TR_SEQ_APPLICATION_SETTINGS AFTER INSERT OR UPDATE ON APPLICATION_SETTINGS REFERENCING NEW AS NEW OLD AS OLD
<snip>

• Tom