Trouble with NT 4.0 and ODBC
Albert Rodes Berenguer -- n7315700@alumnes.eup.udl.es
Monday, November 11, 1996
Environment: Visual C++ 4.0, Windows NT 4.0
Hello. I have some trouble using ODBC under Windows NT 4.0. When I connect to a
datasource (through the Access driver) , and try to read some registers, or do some
SQL query, my application hangs and a message box appears with the text :
"Memory failed (memory position). I Can't read (memory position)"
I think it can be caused by the ODBC driver, which don't work correctly under NT 4.0.
Can anyone help me?
Thanks in advance. Albert.
Anand B Kulkarni -- anand@meghadoot.hiso.honeywell.com
Wednesday, November 13, 1996
[Mini-digest: 4 responses]
Hi,
I have used ODBC under Windows NT 4.0, using Access 7 as the database. I
have had no problems. The driver configured is ODBCJT32.DLL, version
3.40.2829. One possible problem could be that the recordset in your
application is trying to open a very large database, In that case I did
face a problem.
Thanks
Anand B. Kulkarni
anand@hiso.honeywell.com
Albert Rodes Berenguer wrote:
>
> Environment: Visual C++ 4.0, Windows NT 4.0
>
> Hello. I have some trouble using ODBC under Windows NT 4.0. When I connect to a
> datasource (through the Access driver) , and try to read some registers, or do some
> SQL query, my application hangs and a message box appears with the text :
>
> "Memory failed (memory position). I Can't read (memory position)"
>
> I think it can be caused by the ODBC driver, which don't work correctly under NT 4.0.
>
> Can anyone help me?
>
> Thanks in advance. Albert.
-----From: "Dean Wiles"
There was a problem in MFC4.0 with too much allocating memory when
referencing a Memo field in an Access database. This was fixed in a patch
to VC4.0 and in VC4.1 and later. There were also many ODBC / MFC class
fixes in VC4.2.
I have also heard of some Access ODBC fixes for running under NT4.0, but I
don't remember the details. Try checking Microsoft's web site under MS
Office Support.
--------------------------------------------------------------------------
Dean Wiles (deanw@mail.isc-br.com) Olivetti North America
Phone: (509)927-7037 22425 East Appleway Ave
Fax: (509)927-2499 Liberty Lake, WA 99019-9534
If the Son sets you free, you will be free indeed. (John 8:36)
-----From: Vincent Mascart <100425.1337@CompuServe.COM>
Why do you mean by 'read some registers' ? Which MFC classes do you use to 'do
some SQL query' ?
Some code excerpt, especially where the error occurs, would help us to help you
...
Did you try to trace your code to see where it append ?
>I think it can be caused by the ODBC driver, which don't work correctly under
NT 4.0.
I don't agree with you. I use the Access ODBC driver under NT 4.0 without
problem. The only difference I can see in our configuration is the version of
VC++ (4.2flat for me).
>Can anyone help me?
As said previously, help us to help you ...
Vincent Mascart
100425.1337@compuserve.com
-----From: Dong Chen
Which version of the Access database are you using, 32-bit or 16-bit? Make
sure you are using the correspondent driver. You can use the 32-bit ODBC
Admin program to setup your data source for the 32-bit database. I think you
can still run 16-bit ODBC Admin program under NT 4.0 to setup the 16-bit
data source. Another thing you can try is to setup the log file for the data
surce which will keep track of all your ODBC calls.
Also, if you are using ODBC API instead of the CDatabase and CRecordset,
make sure you allocate the connection, environment and statment correctly.
--
Dong
d_chen@ix.netcom.com
| Вернуться в корень Архива
|