Every now and again, each of our developers experiences an issue where Access will crash the first time you try to use intellisense when writing VBA code.

To get back up and running, decompiling the database always fixes the issue, but surely the editor could deal with this by suggesting the user decompiles and recompiles the code, instead of dropping out and potentially losing a lot of unsaved changes.

Example from such a crash -

Faulting application name: MSACCESS.EXE, version: 16.0.13029.20534, time stamp: 0x5f53f9d7
Faulting module name: VBE7.DLL, version: 0.0.0.0, time stamp: 0x5ea725ac
Exception code: 0xc0000005
Fault offset: 0x000256bc
Faulting process ID: 0x3748
Faulting application start time: 0x01d6a38b4a0cc91c
Faulting application path: C:\Program Files (x86)\Microsoft Office\Root\Office16\MSACCESS.EXE
Faulting module path: C:\Program Files (x86)\Common Files\Microsoft Shared\VBA\VBA7.1\VBE7.DLL
Report ID: 14338b0a-4d1f-432d-b845-f3272647ccc1
Faulting package full name:
Faulting package-relative application ID:

For MS Access textboxes on Forms that handle dates you can set the textbox to allow the user to optionally use a built-in DatePicker. However the DatePicker returns the date in a format set by the Windows system (e.g. as Set by Control Panel > Region > |Formats| > [Additional Settings ...] > |Date| > Short Date:)

If you use a unorthodox windows system date format, e.g. "yyyy-/MM-MMM/-dd, ddd" returning "2021/-05-May/-18, Wed" then this can be undesirably returned by the DatePicker.

Instead the DatePicker should return a date that honors any custom format set by in Format property of the Textbox control itself. E.g. If the developer sets an ISO8601 format "yyyy-mm-dd" in the Textbox format property then the DatePicker should return text like "2021-05-18".

For MS Access textboxes on Forms that handle dates you can set the textbox to allow the user to optionally use a built-in DatePicker. However the DatePicker returns the date in a format set by the Windows system (e.g. as Set by Control Panel > Region > |Formats| > [Additional Settings ...] > |Date| > Short Date:)

If you use a unorthodox windows system date format, e.g. "yyyy-/MM-MMM/-dd, ddd" returning "2021/-05-May/-18, Wed" then this can be undesirably returned by the DatePicker.

Instead the DatePicker should return a date that honors any custom format set by in Format property of the Textbox control itself. E.g. If the developer sets an ISO8601 format "yyyy-mm-dd" in the Textbox format property then the DatePicker should return text like "2021-05-18".

EdbMails simplifies Office 365 Migration by automating the configuration and migration tasks. Effectively transfers the data between two Office 365 tenants. It allows you to migrate all the existing mailboxes, contacts and distribution groups, etc. from one Office 365 tenant to another. Its incremental migration feature avoids duplicates on the target mailbox.

Key Features & Advantages:

• It can perform as a single batch move that includes all of your mailboxes, contacts, and distribution group objects, etc.


• Designed with multithreading which improves migration speed and saves lot of time.


• Only the newly added items are migrated to your target server on consecutive incremental migrations which avoids duplicate items.


• Seamlessly migrate your Public folder data to Office 365 with all sub-folders and folder permissions.


• Easy to use user interface, automatic migration (without any Powershell commands) that reduces your time and resources.


• Supported with easy to use GUI, No Powershell commands involved, which reduces your time and resources.


• Automatically maps the source and target mailboxes for the migration operation. In addition, it allows you to manually change/map the target mailboxes.


• Allows moving the recent data with date filter settings and the user can start working with recent emails. Later the rest can be migrated without any downtime.

Not sure if anyone else has run into this issue. The modern charts clustered bar (was what i found this issue on) if the X axis displays a date range and that date range is fixed as month or year or day or quarter and the form is saved then if you have a method that you call in some way that tries to change the dates type (from say month to day or year to month) then this will not action. it runs; but does not actually do anything. If you design the form and change the graphs date range to "None" instead of day,month year.... then when you run your change axis function it works. Design? Bug? the function command by the way is Me.{chart name here}.ChartAxisCollection(0).GroupType = acDateGroupDay