ADODB

  • Thread starter Thread starter Merlin
  • Start date Start date
M

Merlin

Hi,

In VB6 when using ADO e.t.c, it was often required to called the function
db.engine.idle, otherwise MS Access took ages to release record locks and
basically made concurrent use impossible.

Will I suffer the same problems with ADODB in VB.NET? if so is there a
correct method to also implement this function. or does good old ADODB do
all this for me?

Thought I'd enquire as I've found no reference to this and didn't want to be
caught out in the later stages of my project..

Thanks,

Merlin
 
Merlin said:
Hi,

In VB6 when using ADO e.t.c, it was often required to called the function
db.engine.idle, otherwise MS Access took ages to release record locks and
basically made concurrent use impossible.

Will I suffer the same problems with ADODB in VB.NET? if so is there a
correct method to also implement this function. or does good old ADODB do
all this for me?
Click to expand...

As far as I know, ADODB is just a namespace for the ADO COM library. But
symantics aside, I think the ADO.NET people could better awnser this
question:

microsoft.public.dotnet.framework.adonet

HTH,
Jeremy
 
¤ Hi,
¤
¤ In VB6 when using ADO e.t.c, it was often required to called the function
¤ db.engine.idle, otherwise MS Access took ages to release record locks and
¤ basically made concurrent use impossible.
¤
¤ Will I suffer the same problems with ADODB in VB.NET? if so is there a
¤ correct method to also implement this function. or does good old ADODB do
¤ all this for me?
¤
¤ Thought I'd enquire as I've found no reference to this and didn't want to be
¤ caught out in the later stages of my project..

I'm assuming you're referring to DAO (DBEngine.Idle) and not ADO.

ADO.NET operates a bit differently than DAO (and ADO) in that for the most part your data is in a
disconnected state. Whether you use SQL statements, stored procedures or the data objects, updates
operate under optimistic concurrency - which means that locking only occurs for the duration of
database update. There is no supported client-side edit locking mode. Edit locking (pessimistic
concurrency) only occurs at the database (server-side) level.


Paul ~~~ (e-mail address removed)
Microsoft MVP (Visual Basic)
 
Paul Clement said:
¤ Hi,
¤
¤ In VB6 when using ADO e.t.c, it was often required to called the function
¤ db.engine.idle, otherwise MS Access took ages to release record locks and
¤ basically made concurrent use impossible.
¤
¤ Will I suffer the same problems with ADODB in VB.NET? if so is there a
¤ correct method to also implement this function. or does good old ADODB do
¤ all this for me?
¤
¤ Thought I'd enquire as I've found no reference to this and didn't want to be
¤ caught out in the later stages of my project..

I'm assuming you're referring to DAO (DBEngine.Idle) and not ADO.

ADO.NET operates a bit differently than DAO (and ADO) in that for the most part your data is in a
disconnected state.
Click to expand...

This is, of course, depending on what ADO.NET objects you are using & how
you write your data-access layer.
Click to expand...
 
¤
¤ ¤ > On Wed, 9 Jul 2003 12:39:09 +0000 (UTC), "Merlin" <[email protected]>
¤ wrote:
¤ >
¤ > ¤ Hi,
¤ > ¤
¤ > ¤ In VB6 when using ADO e.t.c, it was often required to called the
¤ function
¤ > ¤ db.engine.idle, otherwise MS Access took ages to release record locks
¤ and
¤ > ¤ basically made concurrent use impossible.
¤ > ¤
¤ > ¤ Will I suffer the same problems with ADODB in VB.NET? if so is there a
¤ > ¤ correct method to also implement this function. or does good old ADODB
¤ do
¤ > ¤ all this for me?
¤ > ¤
¤ > ¤ Thought I'd enquire as I've found no reference to this and didn't want
¤ to be
¤ > ¤ caught out in the later stages of my project..
¤ >
¤ > I'm assuming you're referring to DAO (DBEngine.Idle) and not ADO.
¤ >
¤ > ADO.NET operates a bit differently than DAO (and ADO) in that for the most
¤ part your data is in a
¤ > disconnected state.
¤
¤ This is, of course, depending on what ADO.NET objects you are using & how
¤ you write your data-access layer.

Not sure what you're getting at. Do you have an example?


Paul ~~~ (e-mail address removed)
Microsoft MVP (Visual Basic)
 
Back
Top