Access fixes released in versions 2507 and 2508



 Microsoft Access Blog:

Version 2507 (Build 19029.20136)​

Bug NameIssue Fixed
Alert, “The Microsoft Access database engine cannot find the input table or query ‘MSysSQLComments’.” when importing queries from an old database which has never been used with the Monaco SQL editorImporting queries from older databases now works correctly
Queries do not save when they contain Unicode charactersThis happened only with the new Monaco SQL editor and should now work correctly
Error "The Object isn't open" when running Find Duplicates and Crosstab query wizardsThis happened only with the new Monaco SQL editor and should now work correctly
Crash when pressing F1 in Monaco SQL EditorF1 will now launch context sensitive help when used with the Monaco SQL editor
Error “Object is not connected to server” when referencing OLE automation object in VBA codeThis could happen when referencing the OLE object stored in an Unbound Object Frame, such as a PowerPoint slide or Word Document
Crash when opening a query directly into SQL viewThis happened only with the new Monaco SQL editor. All queries should now be able to open successfully directly in SQL view
Images sometimes do not display correctly on buttons/image controlsAll buttons and image controls should now correctly display images
Announce deprecation of Salesforce connectorWe added a callout to let people know about the imminent deprecation of the Salesforce connector

Version 2508 (Build 19127.20154)​

Bug NameIssue Fixed
Control wizards do not launch when adding new controls to subform in design viewThe control wizards will now work when adding a control to a subform
Access terminates unexpectedly when
pressing F6 key in Design View
F6 should now navigate correctly with forms in design view
Unable to select large number (BigInt) field within "Find Unmatched Query Wizard"You can now select Large Number fields in the Find Unmatched Query Wizard
Some wizards giving an error in 32-bit builds on launch “There was an error loading an ActiveX control on one of your forms or reports.”All wizards should now launch correctly
Invalid output when exporting to HTMLSome fields (e.g., number and date/time) were being incorrectly encoded

Please continue to let us know if this is helpful and share any feedback you have.


 Source:

 

Latest Support Threads

Back
Top Bottom