Using ADO with Access2000 & Access97

[Vicky Diamond]

Hello Bill

I just finished converting an application's database from Access97 to Access2000
and noticed a significant performance downgrade, particularly when saving
records. I am using ADO and scoured the code to reduce numbers of connections,
plus many other code adjustmenst such as using serverside cursor with adcmdTable,
just to improve the performance. I also checked the Access2000 database
to make sure that all the indexes and relationships were still intact after
the conversion. But, at the end of the day, after running the same application
code against its Access97 database then running the same code against the
same database after conversion to Access2000, I noticed a significant performance
downgrade. Can you explain why this is occurring and what I can do to improve
the performance?

[Kurtis]

Vicky,

Are you using ODBC to connect or an OLE DB provider?

Kurtis

"Vicky Diamond" <vicky.diamond@dewrsb.gov.au> wrote:
>
>Hello Bill
>
>I just finished converting an application's database from Access97 to Access2000
>and noticed a significant performance downgrade, particularly when saving
>records. I am using ADO and scoured the code to reduce numbers of connections,
>plus many other code adjustmenst such as using serverside cursor with adcmdTable,
>just to improve the performance. I also checked the Access2000 database
>to make sure that all the indexes and relationships were still intact after
>the conversion. But, at the end of the day, after running the same application
>code against its Access97 database then running the same code against the
>same database after conversion to Access2000, I noticed a significant performance
>downgrade. Can you explain why this is occurring and what I can do to improve
>the performance?

[Vicky Diamond]

No. I am using ADO to connect to the OLEDB provider "Microsoft.Jet.OLEDB.4.0".

[Bill Vaughn]

Well, Jet 4.0 switched to Unicode. This means the database itself is twice
as large, it takes twice as many physical IOs to get the rows, they take
twice the memory to cache and the processing takes somewhat longer to work
with (convert back and forth and back again to/from unicode/ansi). Does this
answer your question? To get the performance back... get MSDE.

bv
"Kurtis" <kurtism@kmgroup.net.nospam> wrote:
>
>Vicky,
>
>Are you using ODBC to connect or an OLE DB provider?
>
>Kurtis
>
>"Vicky Diamond" <vicky.diamond@dewrsb.gov.au> wrote:
>>
>>Hello Bill
>>
>>I just finished converting an application's database from Access97 to Access2000
>>and noticed a significant performance downgrade, particularly when saving
>>records. I am using ADO and scoured the code to reduce numbers of connections,
>>plus many other code adjustmenst such as using serverside cursor with adcmdTable,
>>just to improve the performance. I also checked the Access2000 database
>>to make sure that all the indexes and relationships were still intact after
>>the conversion. But, at the end of the day, after running the same application
>>code against its Access97 database then running the same code against the
>>same database after conversion to Access2000, I noticed a significant performance
>>downgrade. Can you explain why this is occurring and what I can do to
improve
>>the performance?
>