2 Attachment(s)
Wierd behavior w/ Microsoft Access database engine 2010 and VB.Net applications
Over the last few months, I've occasionally gotten the following error when starting an application (VB.Net w/MS Access dB):
Attachment 176283
When this happens, the "fix" is to open the Control Panel and repair the Microsoft Access database engine 2010 (English):
Attachment 176285
My system includes Windows 10 (Version 1909, OS build 18363.778), VS 2019 Community (16.5.4 and .NET Framework 4.8.03752), and MS Access 2019 32-bit (16.0.12624.20422).
My applications otherwise has been running without any problems for months, or longer. I don't think the problem is with them. I think it's either a Windows issue (Windows Update?) or MS Access issue.
I have no idea why this error is happening and would appreciate hearing from anyone who has experienced something similar.
Re: Wierd behavior w/ Microsoft Access database engine 2010 and VB.Net applications
As you say, it's not a VB.NET issue so it doesn't belong in the VB.NET forum. If it relates to Access then the Database Development forum might be more suitable, although it's debateable whether it's actually a development question at all, unless the apparent corruption that is occurring is due to your code. I've notified the mods that this thread probably requires moving.
Re: Wierd behavior w/ Microsoft Access database engine 2010 and VB.Net applications
I agree. This sounds like an Access issue, though not one I've run into. Is the database found on the same computer as the program? Access over networks can have some odd issues, though it doesn't usually manifest in this fashion.
Re: Wierd behavior w/ Microsoft Access database engine 2010 and VB.Net applications
Shaggy Hiker,
The Access db is on the same computer as the VB.Net application.
Re: Wierd behavior w/ Microsoft Access database engine 2010 and VB.Net applications
Since it throws Out of Memory: Have you tried starting it while running a ressource-monitor to find out, which process hogs your memory?
EDIT: Can you open your db-file directly with Access?
1 Attachment(s)
Re: Wierd behavior w/ Microsoft Access database engine 2010 and VB.Net applications
Zvoni -
I haven't tried looking at the resource monitor yet, but the next time this error occurs I'll do that. Good suggestion, thanks.
My computer has a lot of RAM.
Attachment 176313
It's hard to believe that the issue is not enough memory, especially when the "fix" has been to repair the MS Access dB engine (not add more memory).
