Access fixes released in versions 2507 and 2508
Version 2507 (Build 19029.20136) Bug Name Issue 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 editor Importing queries from older databases now works correctly Queries do not save when they contain Unicode characters This 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 wizards This happened only with the new Monaco SQL editor and should now work correctly Crash when pressing F1 in Monaco SQL Editor F1 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 code This 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 view This 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 controls All buttons and image controls should now correctly display images Announce deprecation of Salesforce connector We added a callout to let people know about the imminent deprecation of the Salesforce connector Version 2508 (Build 19127.20154) Bug Name Issue Fixed Control wizards do not launch when adding new controls to subform in design view The 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 HTML Some 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.Access releases bug fixes in version 2506
Bug Name Issue Fixed Error when trying to run append query When an update/append query qualified column references (e.g., Table1.Field1) the reference might fail to resolve and produce an error reading “The INSERT INTO statement contains the following unknown field name: Table1.Field1” Error when trying to save or run a query containing certain characters For queries containing some Unicode characters, attempting to run or save the query could generate the error “The SQL statement is invalid.” Can't create a query directly in SQL view We have now added a button to the Queries section of the Create ribbon to allow you to create a new query opened to the SQL editor, rather than the QBE (Query-By-Example) designer Exporting data to a text file might export some characters incorrectly When exporting data containing some Unicode characters and choosing the “Export data with formatting and layout” option, invalid characters would sometimes be output to the text file. Using the clipboard to transfer data from tables/queries to text did not work for some Unicode characters Access was not rendering text from tables/queries with the CF_UNICODETEXT format so when you copied a table/query from the Navigation Pane, then pasted into a destination that accepted text, Unicode characters might not be preserved When exporting to Email using the HTML format Unicode characters might not be preserved Some characters would be replaced by question marks rather than preserving the original content when exporting to HTML Email When exporting a table with a relationship but no lookup defined Access may hang during the validation step During export Access tries to create a lookup in Dataverse that corresponds to a lookup defined in Access for related tables. However, if a relationship was defined but there was no lookup defined for the foreign key, then Access could hang during the export process. If the Display Form option is set in the Options dialog, then any time the Options dialog is closed you incorrectly get a message saying that you must close and reopen the database for changes to take effect This could happen even if no changes were made. Access will now only generate this message if you really do need to close and reopen the database for changes to take effect.
Board Queries suddenly don't filter by states
Hi all, would appreciate your help. I added the "Removed" state to the list of "not in" states, and all of a sudden it doesn't filter all the states. Now the only thing that's filtered is the "Draft" state. After reverting the changes, the query still doesn't work as it did before... It worked fine before making these changes. Any ideas?
Technical Clarifications related to Google Workspace to Microsoft 365 Fasttrack migration!
Hi, We are part of preparatory planning from Google Workspace to Microsoft 365 preparatory planning, it would be great if some help with the below queries w.r.t migration, We want to understand more about Staged/Complete one time cutover along with it's pros/cons While we have referred this https://learn.microsoft.com/en-in/fasttrack/data-migration, below point confirms that share drive membership permissions will not get migrated, my question is what about permissions migration for folders, files with shared drive - Whether it will get migrated or not? "Shared Drive membership permissions (Note: Use Google Drive Admin reports to identify shared drive memberships. Instruct end users to configure these membership settings on the target before migration.)" My next question related to the same https://learn.microsoft.com/en-in/fasttrack/data-migration, below point confirms that formulas will not get migrated, My question is basic formulas like sum, vlookup etc...used in google sheets will not get migrated or only specific formula will not migrated - Need more clarity as our most of the google sheets will have formulas used? "Google Sheets are converted to Excel files, but custom scripts, formulas, and macros are not migrated" My next question related to the same https://learn.microsoft.com/en-in/fasttrack/data-migration, below point confirms that content not owned by google account will not get migrated, My question is what exactly it means - What happens to the data which are owned/created by other domain users as part of collabration? "Content not owned by the Google Drive account being migrated" My next question related to keeping the Google workspace & Microsoft accounts in parallel during & after cutover - How it works technically, can someone through more light here to understand the logic of cutover?
