Re: Executing SQL Statements throught ADO

On Thu, 04 Dec 2003 20:02:25 GMT, "Mark Filson" <mfilson29NOSPAM_at_hotmail.com> wrote:

>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;

 Probably the :new is being interpreted as a placeholder for a bind variable, rather than the literal ':new' that you want as part of the trigger body.

 Not sure of a workaround off the top of my head.

-- 
Andy Hassall (andy@andyh.co.uk) icq(5747695) (http://www.andyh.co.uk)
Space: disk usage analysis tool (http://www.andyhsoftware.co.uk/space)