Conflicts between msJet35.dll and msjet40.dll ...and MDAC versions

  • Thread starter Thread starter kamflam
  • Start date Start date
K

kamflam

we are getting sporadic reboots on our W2000 servers in 3 of our corporate
sites.

There is suspicion that our vb frontend / Jet35 backend apps may be the
cause.
We receive server error 2022 ..which relate to 'unable to find a free
connection'.

We have several W2000 clients, but the majority of clients are still WinNT.
Each of these 1000 PC has a mixture of Jet35 dll's and some have
MSJet40.dll installed as well.
Some have MDAC2.5 ..others 2.6 ..and others 2.7.

Could this mixture of environments lead to excessive or conflicting locking
of databases..which would lead to a REBOOT of the Win2000 Server ???

If so ..the a couple of questions....

1. We have 4000 mdb's in jet3.5 (ie..Access97) and would like to avoid
moving them to Jet4.0 ..since we are soon going to SYBASE. Can we
elegantly UNINSTALL MSJet40.dll on the 40 or so workstations which currently
have it installed in order to get a 'pure' 3.5 environment (assuming that
would be beneficial).

2. Should we standardize on a certain version of MDAC...and if so...what
version should that be ...assuming we standardize on JET35 mdbs for the next
year.

many thanks for any answers...
 
Sorry but I never heard of conflicts between different versions of Jet
actually causing the servver to reboot. The JET database enigine is
actually running on the work-stations which runs the vb front-end and not
your Win2K servers anyway.

Also, are you sure 4000 mdbs is the correct number of databases (not
counting mdbs being used as Access Front-Ends)? If your office are using
4000 databases to store data, it sounds like an exceedingly fragmented
repository of data being used by your office. Or alternatively, the
databases are not used appropriately. I knew a small company that use over
200 databases, one for each of its clients!
 
Each of the 4000 databases represents an 'event' which occurs in a two week
period.
When that event is over, the database is rarely used..and only exists for
historical data.
The problem is, each 'event' database may get as large as 700meg in size.

Anyhow, I realize its the frontend user which determines the database engine
selection.
But some of these frontend clients are WinNT and some are Win2000Pro.
Some have Jet35 (1of 4 versions), some have Jet40 as well (any of 7
versions).

Can the existence of Jet4 dlls cause any problems when we are accessing an
Access97 mdb. ??

Do we know the it will always use the Jet35 dll ??


thx
 
See comments in-line.

--
HTH
Van T. Dinh
MVP (Access)



kamflam said:
Each of the 4000 databases represents an 'event' which occurs in a two week
period.
When that event is over, the database is rarely used..and only exists for
historical data.
The problem is, each 'event' database may get as large as 700meg in size.

Anyhow, I realize its the frontend user which determines the database engine
selection.
But some of these frontend clients are WinNT and some are Win2000Pro.
Some have Jet35 (1of 4 versions), some have Jet40 as well (any of 7
versions).

Can the existence of Jet4 dlls cause any problems when we are accessing an
Access97 mdb. ??
Click to expand...

I used Access2K Front-End to access data in A97 file format so JET 4 should
work fine with A97 file format.


Do we know the it will always use the Jet35 dll?
Click to expand...

I don't use VB but *my understanding* is that the References of your VB
project decide which JET version to use for the VB front-end. Provided you
use the same Front-End for all work-stations, your VB application will use
the (same) JET version (3.5 or 4.0) as specified in the Reference.
 
Back
Top