A form in MS-Access that has worked since 2016 now fails on the report field with =Date() as the control

Given that saving the database using Save As resolved the problem, the most likely cause is corruption in the original.

After trying several suggestions it seems that this particular database lost its connection with the built-in date related functions. Compact and repair the database did not resolve the issue. On opening the report a text box popped up asking for the parameter date; pressing enter opened the report and showed #Name? where the current system date should appear.

What has resolved the problem is saving the database with a different name (Save As) and this new version has worked as intended.

A bit disappointed not fixing the problem in the original database, but will work on that later when more time is available.

There have been some great suggestions. I would open the code window, press Ctrl+G and enter this into the immediate window:

? Date()

Does this display the current date? While in the code, try compile your file from the menu bar.

"Fails" is too vague to be useful in diagnosing the problem and offering suggestions.

Please state what does happen instead of displaying the correct date. An error? The wrong date? Nothing at all?

A screenshot would be helpful.

Also, what version and build of Access do you have installed. You can get that by running this command in the immediate window.

?Syscmd(acSysCmdGetFullVersion)

Microsoft Access (Version 2608) Build 16.0.20326.20144 Current Channel 32-bit

Does this problem appear in every control on every form where this expression is used?
Can you create a new form with one unbound control on it and verify that it happens there as well?
Do you have multiple users? Do all of them have the same error in their copies of the database?The more detail you provide to help us identify potential problems the better the chance of getting a useful suggestion.

Thank you.

Hi @Neville Williams,

The =Date() function is a standard built-in Access function and would not normally stop working without an underlying cause. Since this expression has been working reliably in your reports for many years, it's worth carrying out a few troubleshooting steps before concluding that an update is responsible.

I recommend first performing some troubleshooting within Access:

1. Confirm that the affected control is still an unbound text box and that its Control Source property remains set to: =Date()
   • Open the report in Design View.
   • Click the control that should display the current date.
   • Press F4 if the Property Sheet is not already visible.
   • On the Data tab of the Property Sheet, verify that the Control Source property is set to: =Date()
   • Confirm that the control is an unbound text box and is not linked to a field from the report's record source.
   • On the Format tab, temporarily clear any custom formatting to ensure the value is not being hidden by an invalid format setting.
   • Switch to Print Preview or Report View and verify whether the current date is displayed correctly.
2. Create a new blank report and add a new text box with =Date() as the Control Source. If the new report displays the date correctly while the original report does not, the issue is likely specific to the report or control configuration rather than the Date() function itself.
3. Test other date/time functions such as =Now() to see whether they return values correctly.
4. Run File > Info > Compact & Repair Database to rule out potential database corruption.
5. If the database is split or stored on a network location, test with a local copy to determine whether the issue is environment-specific.

If the issue persists, I would recommend repairing Microsoft 365 Apps:

• Close all office apps completely.   
• Go to Control Panel > Program > Programs and Features   
• Right click on the Microsoft Office you've installed > Change.   

• Select Quick Repair first (fast and doesn’t require internet).   

• If the issue persists, run Online Repair (requires internet and takes longer).   

If the issue continues after an Office repair, and you have presumably confirmed that the behavior started following a Microsoft 365 update, then it would be reasonable to investigate the possibility of an update-related regression. In that case:

• Record the exact Access version and build number from File > Account > About Access.
• Gather details of any errors displayed (for example, #Name?, #Error, blank output, or report generation failures).
• Submit the findings through Microsoft's feedback so the product team can review the behavior.

As a temporary workaround, you may also consider rolling back Microsoft 365 to a previously known working build. If the issue disappears after the rollback, that would help confirm whether a recent update introduced the problem and provide useful information for Microsoft's investigation.

If you need any further assistance, please don't hesitate to leave a comment.

Kind Regards,