VB & Database, microsoft.jet.oledb.3.51 v.s. microsoft.jet.oledb.4.0

microsoft.jet.oledb.3.51 v.s. microsoft.jet.oledb.4.0

Author	Message
MLL #1 / 3	microsoft.jet.oledb.3.51 v.s. microsoft.jet.oledb.4.0 I am running Windows NT 4.0 and I upgraded to Access 2000 so in the example code below I ONLY changed microsoft.jet.oledb.3.51 to microsoft.jet.oledb.4.0. When the program uses microsoft.jet.oledb.4.0 it runs 3 times slower than microsoft.jet.oledb.3.51 to perform the same updates. Any ideas why this happens and what I can do to fix it? 'Example Code----------------------------------------------- Dim conCCIWorking As New ADODB.Connection Set conCCIWorking = New ADODB.Connection conCCIWorking.Open "provider = microsoft.jet.oledb.3.51 ; data source= c:\w\working.mdb;" Set rsCCIWorking = New ADODB.Recordset With rsCCIWorking .ActiveConnection = conCCIWorking .CursorType = adOpenStatic .LockType = adLockPessimistic End With '-------------------------------------------------------------- Mel --------------------------------------------------- Circuit Check, Inc. Maple Grove, MN 55311 www.circuitcheck.com "The largest single-facility manufacturer of custom test fixtures and related products for automatic test equipment." ---------------------------------------------------
Mon, 05 Jul 2004 05:08:23 GMT

Val Mazu #2 / 3	microsoft.jet.oledb.3.51 v.s. microsoft.jet.oledb.4.0 Hi, Next article could give you some hints http://www.able-consulting.com/ADO_Faq.htm#Q16 Val Quote: >-----Original Message----- >I am running Windows NT 4.0 and I upgraded to Access 2000 so in the example >code below I ONLY changed microsoft.jet.oledb.3.51 to >microsoft.jet.oledb.4.0. When the program uses microsoft.jet.oledb.4.0 it Quote: >runs 3 times slower than microsoft.jet.oledb.3.51 to perform the same >updates. Any ideas why this happens and what I can do to fix it? >'Example Code--------------------------------------------- -- >Dim conCCIWorking As New ADODB.Connection >Set conCCIWorking = New ADODB.Connection >conCCIWorking.Open "provider = microsoft.jet.oledb.3.51 ; data source= >c:\w\working.mdb;" >Set rsCCIWorking = New ADODB.Recordset >With rsCCIWorking > .ActiveConnection = conCCIWorking > .CursorType = adOpenStatic > .LockType = adLockPessimistic >End With >'--------------------------------------------------------- ----- >Mel >--------------------------------------------------- >Circuit Check, Inc. >Maple Grove, MN 55311 >www.circuitcheck.com >"The largest single-facility manufacturer of custom test fixtures and >related products for automatic test equipment." >--------------------------------------------------- >.
Mon, 05 Jul 2004 06:11:14 GMT

MLL #3 / 3	microsoft.jet.oledb.3.51 v.s. microsoft.jet.oledb.4.0 In the article it says I should upgrade the system database (.MDW) (I am not using ODBC). What is the system database .MDW? Quote: > Hi, > Next article could give you some hints > http://www.able-consulting.com/ADO_Faq.htm#Q16 > Val > >-----Original Message----- > >I am running Windows NT 4.0 and I upgraded to Access 2000 > so in the example > >code below I ONLY changed microsoft.jet.oledb.3.51 to > >microsoft.jet.oledb.4.0. When the program uses > microsoft.jet.oledb.4.0 it > >runs 3 times slower than microsoft.jet.oledb.3.51 to > perform the same > >updates. Any ideas why this happens and what I can do to > fix it? > >'Example Code--------------------------------------------- > -- > >Dim conCCIWorking As New ADODB.Connection > >Set conCCIWorking = New ADODB.Connection > >conCCIWorking.Open "provider = microsoft.jet.oledb.3.51 ; > data source= > >c:\w\working.mdb;" > >Set rsCCIWorking = New ADODB.Recordset > >With rsCCIWorking > > .ActiveConnection = conCCIWorking > > .CursorType = adOpenStatic > > .LockType = adLockPessimistic > >End With > >'--------------------------------------------------------- > ----- > >Mel > >--------------------------------------------------- > >Circuit Check, Inc. > >Maple Grove, MN 55311 > >www.circuitcheck.com > >"The largest single-facility manufacturer of custom test > fixtures and > >related products for automatic test equipment." > >--------------------------------------------------- > >.
Mon, 05 Jul 2004 21:19:03 GMT

Page 1 of 1

[ 3 post ]