I just got this error while doing testing yesterday. The reason I was
getting the error was the query I was running was working with too many
records. I was doing a db.Execute "DELETE * FROM Table WHERE Blah. This
was attempting to delete 440,000 records from a table. To get around it I
put the commit statement in the errorhandler, and then ran the query again.
I have also seen this when attempting to do cascades over many tables with
thousands of records. You may want to examine the size of the data you are
working with. It's a place to start.
--
TNB (Tim Walsh - You might find me in the yellow pages!)
> I realize there is some additional information that would be helpful here.
> In our report dll we are using jet 3.6 to create a dao database connection
> between the vb report dll and the access database. Most of the servers
> where this problem is occurring are Windows 2000 Servers with MDAC2.5. I
am
> not sure that all of the servers are on the latest Service Pack for
windows
> 2000. Further we are using Oracle 8i Client libraries to connect our
> service to the Oracle DB using OCI. I have a suspicion that this problem
is
> related to some incompatability or conflict between the services OCI
> connection to the database and the vb dll's dao connection to the access
> database. In environments that are running against a SQL Server
> environment, this has never been a problem.
> > I have an application that creates reports from a VB DLL. On occasion I
> > will get an error such as "System Resource Exceeded". I can run my
report
> > again and everything seems to complete correctly. This report dll is
> being
> > instantiated by a service that is running on Windows 2000. Further the
> > process has an OCI connection to an Oracle database where it retrieves
> > certain information which it then writes into an Access MDB for use by
the
> > report dll.
> > Any ideas on what might be causing this problem.
> > Thanks,
> > Joel