[phplib] Yet Another M$ Access Gothcha From: Brian Popp (bpopp <email protected>)
Date: 08/10/01

This is just an FYI for those of you implementing Access solutions.

I just took us off IIS and switched us to Apache (using the PHP Module).
Everything went smooth, but unfortunately, some of my ODBC (Access) PHPLib
apps started dying with a 'Too many client connections' error. Turns out,
the Jet Database engine limits you to 10 concurrent connections per process.
So in the case of servers using ISAPI, only 10 concurrent connections would
be allowed at once (assuming each page only uses one connection).

I don't have a ton of users so this is ok, but you also have to make sure
you free your results. Otherwise, the connection apparently stays open until
it times out. It seems to be working OK now that I've set "AutoFree=1" in my
db_odbc.inc file.

-----Original Message-----
From: Dr Tarique Sani <tarique <email protected>>
[mailto:tarique <email protected>]
Sent: Wednesday, August 08, 2001 8:19 AM
To: Taylor, Stewart
Cc: phplib <email protected>
Subject: RE: [phplib] Another M$ Access Gothcha

On Wed, 8 Aug 2001, Taylor, Stewart wrote:

> You could also do a manual $field = str_replace("'","''",$field)
> on your fields

Yes and if you want to over kill ereg_replace BUT the point is that both
these methods are a kludge / hack if you cannot get to the php.ini file, I
wouldn't consider this the "proper" way ;-)

In fact this was the first thing which came to my mind

Cheers
Tarique 

-- 
=========================================
       B2B Application Providers
        http://www.sanisoft.com
 Vortal for Nagpur http://nagpurcity.net
=========================================

-- 
Abbestellen mit Mail an:   phplib-unsubscribe <email protected>
Kommandoliste mit Mail an: phplib-help <email protected>

-- 
Abbestellen mit Mail an:   phplib-unsubscribe <email protected>
Kommandoliste mit Mail an: phplib-help <email protected>