-
Notifications
You must be signed in to change notification settings - Fork 154
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Not enough memory" Error during ODBC Update in MS Access 2.0 #1023
Comments
Lock 60 means the memory is page locked and globalrealloc doesn't permit the block to move if pagelockcount is greater than 0. It calls GetVDMPointer32W which calls globalpagelock but never calls globalpageunlock. |
Hello, Best regards. |
Try #1024 |
Hello, |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
I get an error "Not enough memory" if I try to update a column in a bound table (Oracle database) in MS Access 2.0
(see trace). This database update works, if I use the same Access 2.0-mdb with the NTVDM in Windows XP.
I Use the 32-Bit ODBC-Driver from Oracle (V12.1 with OTVDM in Windows 10 and V11.2 with NTVDM in Windows XP)
Not sure if this is really a OTVDM problem, but maybe you can clarify this.
Gettings from germany
Trace.zip
The text was updated successfully, but these errors were encountered: