MSACCESS App Crash

[Docent24]

Hi, Cristian.

First of all, a HUGE THANK YOU for this wonderful project. It does everything we need and some extra =))

But after inspecting windows error logs from different workstations, we noticed dozen records like

Faulting application name: MSACCESS.EXE, version: 15.0.5349.1000, timestamp: 0x6087e5d4
Faulting module name: scrrun.dll_unloaded, version: 5.812.10240.16384, timestamp: 0x39e8991c
Exception code: 0xc0000005
Fault offset: 0x00012290
Faulting process ID: 0x27d4
Faulting application start time: 0x01dca557f6d345bc
Faulting application path: C:\Program Files (x86)\Microsoft Office\Office15\MSACCESS.EXE
Faulting module path: scrrun.dll

Such records was not the case with scrrun native dll.

I was unable to reproduce the error, just want to let you know about it. Maybe you have some suggestions where we can start to pinpoint the problem.

MSACCESS Project have scrrun reference for FSO use, ACCDE compiled, OS Win 10 64 bit mostly, Office is 32 bit.

Thanks!

[cristianbuse]

Hi @Docent24

Thank you for the kind words and feedback!

All the tests I've created so far are passing on MSACCESS so this must be something I have not thought about.

Since you are having both this dictionary and the scripting one at the same time, I would suggest the following steps:

1. remove the reference to Scripting (scrrun)
2. save and close the project
3. reopen and add back the reference to Scripting

This would force VBA to recognise the dictionaries properly.
Does this solve the issue?

Thanks!

[Docent24]

It will take some time to test "in the field", i will get back with the results.

We use FastDictionary over a year now, and the project was rebuilded a couple of times with VCS add-in and problem is still there. As i can see, VBA choose "the right one" Dictionary object, as there are no errors with FastDictionary specific methods and project compiles just fine.

However, if you suspect that root cause of problem might be the reference to scrrun.dll - perhaps I could try to use Late binding for FSO call and remove the reference completely. Thanks for the tip, will try that one.

[cristianbuse]

Yes, absolutely it could be the problem. I had crashes (Excel) when having both Dictionaries but they went away as soon as I removed and added the reference back.