S
Steve
Hi all.
I've searched this newsgroup for similar postings and they all seem
to
be under a slightly different scenario than what I'm experiencing.
I have an application with my own User Security file (BB.MDW) which
is
used to access several secured access databases. The workgroup file
resides in the same directory as the .mdb files with a different name
than the .mdb files.
What happens, though, is several users will be running fine and
accessing the databases without problems and subsequent users will
attempt to access the secured database(s) and encounter the error.
The applications are being run within an Application Pool. The
application pool processes have the proper permissions to the
directory where the .mdb and .mdw files reside so I know it's not a
file permissions issue.
Also, I'm pretty confident that the BB.MDW file is not corrupt
because
the users tell me that the problem clears up when: 1) Application
Pool
is restarted; 2) system is rebooted; 3) left alone for a while.
This leads me to believe the cause of the problem is due to a maximum
number of users connecting to the workgroup (or .mdb) file. To test
this theory, I created a simple VB application that used ADO to
create
an array of open ADODB.Connection objects against my database using
the BB.MDW to see if there is a limit on open connections and after
64
connection objects I received an ADO error of 'Unspecified
error' (-2147467259).
Would the "cannot open workgroup informatino file" error still occur
if the User workgroup file is not corrupted but the system.mdb/.mdw
is
bad?
Does anyone else have any suggestions as to why this error message
may
occur and affect some users but not all users?
I'm running out of ideas on what else may cause this problem since
the
suggestions provided in other postings don't quite fit my scenario.
Thanks in advance for any and all suggestions.
Steve Cummings
I've searched this newsgroup for similar postings and they all seem
to
be under a slightly different scenario than what I'm experiencing.
I have an application with my own User Security file (BB.MDW) which
is
used to access several secured access databases. The workgroup file
resides in the same directory as the .mdb files with a different name
than the .mdb files.
What happens, though, is several users will be running fine and
accessing the databases without problems and subsequent users will
attempt to access the secured database(s) and encounter the error.
The applications are being run within an Application Pool. The
application pool processes have the proper permissions to the
directory where the .mdb and .mdw files reside so I know it's not a
file permissions issue.
Also, I'm pretty confident that the BB.MDW file is not corrupt
because
the users tell me that the problem clears up when: 1) Application
Pool
is restarted; 2) system is rebooted; 3) left alone for a while.
This leads me to believe the cause of the problem is due to a maximum
number of users connecting to the workgroup (or .mdb) file. To test
this theory, I created a simple VB application that used ADO to
create
an array of open ADODB.Connection objects against my database using
the BB.MDW to see if there is a limit on open connections and after
64
connection objects I received an ADO error of 'Unspecified
error' (-2147467259).
Would the "cannot open workgroup informatino file" error still occur
if the User workgroup file is not corrupted but the system.mdb/.mdw
is
bad?
Does anyone else have any suggestions as to why this error message
may
occur and affect some users but not all users?
I'm running out of ideas on what else may cause this problem since
the
suggestions provided in other postings don't quite fit my scenario.
Thanks in advance for any and all suggestions.
Steve Cummings