Thank you for the replies. It turn out to be a code issue. The developer added
olecmd.dispose(), which fixed the problem.
[EMAIL PROTECTED] 07/28/03 11:54AM
There are some relevant notes on MetaLink that may be of help.
Search on 'visual basic ora-1000'
Jared
On Monday 28 July 2003
We have a developer that is inserting a large number of records using a VB program.
An insert trigger exists on the table. This trigger checks a parent table for
records. I know this trigger really is not needed, since a Foreign Key exists to
enforce referential integrity, so I plan to
Title: RE: Maximum Open Cursors on Insert Trigger
Just for a more _completeness_ I'd put a curser close statement in the exception clause ... I agree with you that for-update is a no no in this context.
Raj
There are some relevant notes on MetaLink that may be of help.
Search on 'visual basic ora-1000'
Jared
On Monday 28 July 2003 07:54, Jay Hostetter wrote:
We have a developer that is inserting a large number of records using a VB
program. An insert trigger exists on the table. This trigger
