By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
445,704 Members | 1,867 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 445,704 IT Pros & Developers. It's quick & easy.

Simultaneous VB.Net and Access on Jet 4.0

P: n/a

We have an application supplied to us from an outside source in the
form of a VB .Net front end and a Jet 4.0 back end database. We also
have various internally developed applications in Access 2003 which
connect to this back end database as well via linked tables. In
addition to the linked tables some of the internally developed
applications have a global DAO database object which connects to that
database when the application is started and which is not relinquished
until the application is closed. The back end database resides on a
Win2k server and all the various front ends reside on individual
workstations. All of this works harmoniously up to a point. It seems
that after we have a few Access users connected to the database the VB
..Net application's performance degrades considerably, e.g. an
operation that normally might take 8-10 seconds by the VB application
will suddenly take up to three minutes to complete. The Access users
don't notice any performance hit at all. I haven't been able to
solidly test this to determine that the Access connection to the back
end database is causing the problem, but there's enough circumstantial
evidence pointing to it to make me very suspicious. Has anyone else
out there had experience with this sort of scenario? I don't know how
the VB app is connecting to the database (ADO, ADO.Net, etc...) but
are there known problems with simultaneous DAO and non-DAO access to
the same Jet database? I have some contact with the developer of the
VB app but I don't know what questions I should ask about how he's
attaching to that database. Any pointers/help greatly appreciated.

Nov 12 '05 #1
Share this Question
Share on Google+
1 Reply

P: n/a
I know exactly what your problem is. has way more horsepower
than vba or vb6 and thus takes way more gas. If you have multiple users
on an access mdb and also connect to the .net app, there won't be enough
gas for the .net app. You're would be way better off with sql server if
you want to use .net and multiple concurrent users. .Net & sql Server
:). With all due respect to Access, when Access is the backend (instead
of the front end - which Access is a front end development tool) and
used with VB.Net, that is like powering a 4 cylinder pickup truck with a
turbine engine from an F14.


*** Sent via Developersdex ***
Don't just participate in USENET...get rewarded for it!
Nov 12 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.