On Wed, 09 Jul 2003 14:00:50 GMT, "Jeremy Cowles" <je*************************@asifl.com> wrote:
¤
¤ "Paul Clement" <Us***********************@swspectrum.com> wrote in message
¤ news:is********************************@4ax.com...
¤ > On Wed, 9 Jul 2003 12:39:09 +0000 (UTC), "Merlin" <je**@jg-tech.co.uk>
¤ 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 ~~~
pc******@ameritech.net
Microsoft MVP (Visual Basic)