Refresh of my project consistently crashes MsAccess

[MichielfromNL]

Rubberduck version information

Rubberduck version 2.5.9.6316 loading:
Operating System: Windows 10 Pro 2009 x64 (Microsoft Windows NT 10.0.26100.0)
         (windows 11 Pro 24H2)
Host Product: Microsoft Office x64
Host Version: 16.0.18925.20184
Host Executable: MSACCESS.EXE;
    System has 32Gb memory

Description
I am a first time user, just installed and ran Rubberduck on my current project consisting of approx 30 Forms with VBA, 20 modules, 25 classes. All have option explicit, no compile errors.
When I run "refresh", ms access concistently crashes after approx 15 seconds.

To Reproduce

1. Open Access.
2. Open VBE
3. run Refresh
   Ms access crashes after approx 15 seconds of activity

Expected behavior
No Msaccess crashes

Screenshots
N/a.

Logfile
Attached

Additional context
n/a

RubberduckLog - Crash.txt

[retailcoder]

The number of modules, syntax/compilation errors, or whether implicit declarations exist or not, would not crash Rubberduck / the host process.

Was Access installed as part of Office / Microsoft 365? Are there different versions of Office running side by side on the system, and were they installed in sequential release order? For example if you have Office 2022 but later installed Visio 2013, chances are there's a COM component that was corrupted in the process, and per Microsoft it isn't a supported scenario; reinstalling Office may fix it.

Are there other add-ins in the process that could be interfering in obscure ways? What I'm getting at is that many things can cause a crash, that are well beyond our control.

[MichielfromNL]

Thanks for your reply.
My installation is pretty vanilla, nothing out of the ordinary, Especially on Windows I try to avoid anything non-standard as the plague.
There are no other VBE add-ins, Office is standard and up to date 365 desktop .
I would love to find out what is going on but I have little to start with at this time... Suggestions and hints are welcome.

[pflugs30]

I've done quite a bit of development in MSAccess using Rubberduck. I have seen several cases where my databases become corrupt and unstable through no fault of RD. You can try a Compact and Repair, and you might need to build a new, blank database and then migrate all your objects into the new database. With a few of the production-level databases which I maintain for my clients, I run into this situation so often that I built automation tools for this purpose.

This answer might not be what you want to hear, but it might be something to try.

[MichielfromNL]

Got is, and agree, MsAccess has such flaws.
So I followed your advice, used https://github.com/joyfullservice/msaccess-vcs-addin to export /import all and start fresh, and indeed no more crashes..

But now the next issue: RD fails to parse with "resolver error". Checked similar issues here but found no clues to pinpoint what happens and why. I will post that in other more relevant threads
Tx sofar

[pflugs30]

Really quick reply because I have some things to do this evening... are you missing any references? Otherwise, post some screenshots or log outputs.

…

On Wed, Jul 30, 2025 at 5:16 PM Michiel Steltman ***@***.***> wrote: *MichielfromNL* left a comment (rubberduck-vba/Rubberduck#6284) <#6284 (comment)> Got is, and agree, MsAccess has such flaws. So I followed your advice, used https://github.com/joyfullservice/msaccess-vcs-addin to export /import all and start fresh, and indeed no more crashes.. But now the next issue: RD fails to parse with "resolver error". Checked similar issues here but found no clues to pinpoint what happens and why. I will post that in other more relevant threads Tx sofar — Reply to this email directly, view it on GitHub <#6284 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABBUPOASUWDKO25DKRJJSDD3LE743AVCNFSM6AAAAACCWMBDIWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCMZXHE4DIMRXGY> . You are receiving this because you commented.Message ID: ***@***.***>

[MichielfromNL]

References are fine, I have a module to check for broken links.
Attached the log. Can't really pinpoint where the fails trigger (yet), from the log info it is not clear (to me at what module / line the problems happen. As far as I can see there are several spots where the parsing / resolving fails. Pointers into how to analyse this further would be helpfull!

RubberduckLog - Resolver error.txt

[pflugs30]

I forgot to ask. After you rebuilt the Access database, does the VBIDE still compile the code without errors? I'd assume so given what you said above, but it's best to ask directly.

[MichielfromNL]

Yes, 100%, I have option explicit in all my modules

[Vogel612]

@MichielfromNL having Option Explicit is a good start, but that wasn't actually the question. The VBE is a bit nasty and it avoids compiling code as much as it can, which can lead to code not actually being compilable, but that only comes out when the relevant module is actually run.

Rubberduck does not know about what the VBE didn't actually look at and tries to look at all modules. This sometimes results in issues...

That being said, the logs suggest that the Resolver is struggling on a SingleLineIfStatement within UtcConverter. Rubberduck is also correctly recovering from a difficult to parse function in that module earlier in the logs, so I suggest you take a closer look at that particular one and try playing around a bit, maybe we can narrow down the issue to something more minimal :)

[MichielfromNL]

Thanks for the hint to look where, found it !!
It was this line:

If utc_NegativeOffset Then: utc_Offset = -utc_Offset
note the colon, changed to
If utc_NegativeOffset Then utc_Offset = -utc_Offset

Parses without problems now!
Hope that helps!

Michiel
Edited: same problem as in #6187 (comment) , my solution was removing the ":"