Re: problems with DSN for MS Acess database
- From: "Sky" <sky@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 20 Dec 2005 05:35:00 GMT
<kdv09@xxxxxxxxxx> wrote in message
news:1135054932.284450.211830@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
....
> After that by silly mistake User DSN for MS Access Database was created
> on the development PC (the one with existing and working MS Access).
> This upset performance of database access very badly - it takes very
> long time to read and move through the records
You could check the Advanced parameters in the ODBC setup.
Or you could extract the registry entries and compare them between the two
computers. To do this, open RegEdit and look at the keys for:
[HKEY_CURRENT_USER\SOFTWARE\ODBC\ODBC.INI\YourOdbcDsN]
if it is a User DSN,
or
[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\YourOdbcDsN]
if it is a System DSN.
You can use RegEdit File Export to save text files for these keys and
compare the results.
If you have both User and System DSN, the User DSN wins, when you connect in
C++ using ODBC.
One parameter to check is buffer size, located at:
[HKEY_CURRENT_USER\SOFTWARE\ODBC\ODBC.INI\YourOdbcDsN\Engines\Jet]
"MaxBufferSize"=dword:00008000 ; or whatever size you want
- Steve
.
- Follow-Ups:
- Re: problems with DSN for MS Acess database
- From: kdv09
- Re: problems with DSN for MS Acess database
- References:
- problems with DSN for MS Acess database
- From: kdv09
- problems with DSN for MS Acess database
- Prev by Date: problems with DSN for MS Acess database
- Next by Date: Re: problems with DSN for MS Acess database
- Previous by thread: problems with DSN for MS Acess database
- Next by thread: Re: problems with DSN for MS Acess database
- Index(es):
Relevant Pages
|
Loading