I might be way off here but didn't you say you were using driver 2.7, is
there not a much newer ODBC driver you could try. And for testing
purposes pump up the connections in your cache to see what happens.
-----Original Message-----
From: "Michael J. Cook" <[EMAIL PROTECTED]>
To: "sambar List Member" <[EMAIL PROTECTED]>
Date: Fri, 06 Dec 2002 21:06:22 -0500
Subject: [sambar] System Resource Exceeded {03}
> Jeff Adams wrote:
>
> > At 07:42 PM 12/06/2002 -0500, Michael J. Cook wrote:
> >
> > >Now the theory...
> > >
> > >Windows ODBC is built to work with the Win2k OS (obviously). The OS
> sees
> > >the 10
> > >connection limit that the ODBC is trying to exceed, refuses
> additional
> > >connections, and somehow kills ODBC and/or Sambar dbms stops
> responding.
> > >
> > >If I'm way out in left field, start calling me back in right now
> ;-))
> >
> > I believe Sambar is making the ODBC calls and as such, the 10
> connection
> > limit does not apply because the calls are local. The web requests
> from
> > the remote clients that make those requests do not actually count as
> > file/print connections. Where you might see this apply is if more
> than 10
> > clients had direct ODBC links to a database housed on your computer.
> In
> > that case, the connections would count as file share connections.
> >
> > -Jeff
> > -------------------------------------------------------
> > To unsubscribe please go to http://www.sambar.ch/list/
>
> Doh! Of course. I forgot that the ODBC calls are local to the
> machine. Well,
> I'm fresh out of theories as to the 10 connection limit. Unless
> Microsoft's
> ODBC drivers impose the 10 connection limitation?
> -------------------------------------------------------
> To unsubscribe please go to http://www.sambar.ch/list/
>
>
-------------------------------------------------------
To unsubscribe please go to http://www.sambar.ch/list/
