access
1921 TopicsZoom in or out of forms, tables, and queries when in Form View or Datasheet View
Access now lets you zoom in and out when you’re working with forms, tables, and queries in Form View or Datasheet View. Zoom in for a closer look at your data or zoom out to see more on screen at once. You can adjust the zoom level using the Zoom button on the ribbon, the zoom slider on the status bar, or keyboard shortcuts. Zoom is also available in Print Preview for reports. Zoom isn’t supported in Report View or Design View. This feature is available in Access for Microsoft 365, version 2605 and later. Choose a magnification setting from the ribbon On the Home tab, select Zoom and choose one of the following options: 50%, 75%, 125%, 150%, 175%, 200%, or 500%. To return the view to 100% zoom, click Zoom 100%. If you prefer to use the keyboard, you can press Ctrl + Alt + 0 (zero). Use the zoom slider to quickly zoom in or out On the status bar in the lower right-hand corner of Access, select the zoom slider. Slide to the percentage zoom setting that you want. Press – or + to zoom in gradual increments. Use zoom keyboard shortcuts or mousewheel To zoom in, press Ctrl + Alt + Plus (+). To zoom out, press Ctrl + Alt + Minus (-). To return to 100% magnification, press Ctrl + Alt + 0 (zero). To use the mousewheel and scroll to zoom in or out, press Ctrl + mousewheel. Change your default zoom percentage Access doesn't save zoom settings on closing and reopening a form. Instead, it opens your form using the default zoom setting. To set your zoom default percentage, choose File > Options > Current Database > Application Options and choose the Default Zoom setting. Note Content inside of ActiveX controls, such as the text in a TreeView control, doesn't resize when zoomed. Zooming in Access only affects Access-native controls. If a form uses ActiveX controls, consider replacing them with native Access controls so they scale with the rest of the form.56Views0likes0CommentsMicrosoft 365 E5 Developer Program Phone Number Issue
I have been trying to set up my a developer program account to play around it and test things but when I try to sign up for it It says that my phone number is already in use and that I can't use it. I don't really remember creating a developer program account and I understand that your only allowed to have one but none of my accounts that I have access too seem to be the one that it's linked too. I've exhausted every other method to try and fix it so I am resorting to posting this here in hopes that somebody has some insight into how to fix this.3Views0likes0CommentsAccess fixes released in Version 2603 (Build 19822.20114)
Here's a summary of bug fixes in the latest version of Access: Bug Name Issue Fixed Edge Browser Control didn't navigate from code when inside a tab control When the Edge Browser control was hosted in a tab control, calls to the Navigate method from VBA succeeded, but the control didn’t refresh to show the new page. Switching tabs forced the refresh. The control now refreshes automatically after navigation, even when it’s hosted in a tab control. Some Unicode characters displayed incorrectly in Quick Import Certain extended Unicode characters were displayed as squares when importing data using Quick Import. These characters are now displayed correctly. Modern Chart titles truncated in Print Preview When viewing a report containing Modern Charts in Print Preview, chart titles might be truncated. Chart titles now render correctly in Print Preview. Some Unicode characters displayed incorrectly in exported object names When exporting an object whose name contained certain extended Unicode characters, the sheet name in the exported file displayed the characters incorrectly. These characters are now preserved correctly during export. Some Unicode characters displayed incorrectly in error messages for long object names When renaming a database object to a name that was too long, the error message displayed certain extended Unicode characters incorrectly. These characters now display correctly in error messages. Standard colors in Access didn't match other Office apps The standard color palette in Access used different color values than other Office applications like Word and Excel. For example, the standard red in Access was #ED1C24 instead of the updated Office standard red #EE0000. The color palette has been updated to match the rest of Office. Field.Properties("Precision") and Properties("Scale") on a query column caused the query to execute Accessing the Precision or Scale properties of a field in a query's Fields collection caused the query to execute. This was a regression that broke add-ins and code that enumerate field properties, since query execution can be expensive and have side effects. These properties are now returned without executing the query. Toggle filter button in status bar didn't work when no records were displayed When a form filter resulted in no matching records, clicking the Toggle Filter button in the status bar to remove the filter had no effect. The button now properly removes the filter even when the filtered result set is empty. PDF files with capitalized extension didn't render in Edge Browser Control When navigating to a PDF file using the Edge Browser control, if the file extension was capitalized (e.g., ".PDF" instead of ".pdf"), the file contents were rendered as raw text instead of as a formatted PDF document. The extension comparison is now case-insensitive. Monaco SQL editor inserted blank lines in multi-line comments When switching between Design View and SQL View, the Monaco SQL editor inserted blank lines between each line inside /* multi-line comment */ blocks. This affected both local and passthrough queries. The editor now preserves the original comment formatting. Please continue to let us know if this is helpful and share any feedback you have.606Views2likes2CommentsStumped on auto populate staying in a combo box
This is embarrassing. I’ve been building databases since 1999 and now I’m stumped I have an MS Access database with a combo box that is used to select specific records. These records have two particular fields. A primary key named “Track” and a value associated with it called FTitle. Track is a numeric field and FTitle is text. FTitle shows the job title. I had this working beautifully on a database for six years. Go into the combo box, start typing in the FTitle and it would auto populate with an FTitle name. I've checked everything. Auto expand and everything else Two things are happening here. I cannot get an autopopulate combo box to work. It works when I make it. Then when I reopen the form it stops working. I tried to add options to the existing front end which autopopualted perfectly. It seems that when I added a subform to the form the combo box auto populate on stopped working. Any advice??71Views0likes2CommentsAccess fixes released in Version 2604 (Build 16.0.19929.20090)
Bug Name Issue Fixed Values display in the wrong control when using a form as a sublist When a form was used as a sublist (subdatasheet), field values could display in the wrong control, showing data in incorrect positions. Values now display in the correct controls. Applications that use the Access Database Engine (ACEOLEDB) terminate unexpectedly on exit Third-party applications using the Access Database Engine (ACEOLEDB) provider could terminate unexpectedly when closing. The shutdown sequence has been corrected. Long Text field corrupted when a query updates a record while a user is editing it When a query updated a Long Text field on a record that was simultaneously open for editing, the field data could become corrupted. The record update now correctly handles concurrent access to Long Text fields. Rendering errors with Aptos (Detail) font Controls using the Aptos (Detail) font variant could render incorrectly, with characters appearing misaligned or garbled. The font rendering has been corrected. Standard colors in Access didn't match other Office apps The standard color palette in Access used different color values than other Office applications like Word and Excel. The color palette has been updated to match the rest of Office. Option Group with Vertical Anchor Bottom: option buttons show incorrect visual state after clicking When an option group control had its Vertical Anchor property set to Bottom, clicking an option button would not correctly update the visual state of the buttons. The visual state now updates correctly regardless of the anchor setting. Query Design: Insert/Delete Columns don't work when ribbon is set to Show Tabs Only In Query Design view, the Insert Columns and Delete Columns commands on the ribbon did not work when the ribbon display option was set to "Show Tabs Only." The commands now work correctly regardless of ribbon display mode. SQL View: Ctrl+K should toggle pretty formatting off/on In the Monaco SQL editor, the Ctrl+K keyboard shortcut did not toggle SQL formatting. Ctrl+K now correctly toggles pretty formatting on and off. Monaco editor incorrectly converts Unicode characters in SQL view When switching between Design View and SQL View, the Monaco SQL editor could incorrectly convert certain Unicode characters, corrupting the SQL text. Unicode characters are now preserved correctly. Importing text files with Unicode characters in the filename fails Attempting to import a text file whose filename contained certain Unicode characters would fail. File imports now handle Unicode filenames correctly. Added VarP and StDevP to the Totals query aggregate dropdown The VarP (population variance) and StDevP (population standard deviation) aggregate functions were missing from the Totals row dropdown in Query Design view. They have been added alongside the existing Var and StDev options. Added VarP and StDevP to the datasheet totals row dropdown The VarP and StDevP aggregate functions were missing from the Totals row dropdown in Datasheet view. They have been added to match the options available in Query Design view. Access hangs at shutdown when VBA holds temporary DAO field references Access could hang during shutdown when VBA code created temporary DAO field references. The shutdown process now correctly cleans up temporary field references. Full Screen Mode ribbon display option does nothing in Access Selecting "Full Screen Mode" from the ribbon display options had no effect in Access. This option now works correctly, hiding the ribbon to maximize the available workspace.1.4KViews3likes6CommentsODBC error (incorrect syntax) since 2604
Overnight i have the problem that many inserts in my MS Access app do not work anymore. I get the error Run-time error '3155': ODBC--insert on a linked table 'tablename' failed. [Microsoft][ODBC SQL Server Driver][SQL Server]Incorrect syntax near '='.(#102) I have been able to isolate this issue on a column of type NVARCHAR(MAX). If I insert any value except null in this column the error above will show on save. I tested with other variants of NVARCHAR. The problem happens starting from NVARCHAR(256), thus what is Long Text for Ms Access. When i insert the record first with a value null for this column, no error is generated and the record is saved. If i 'Update' the record later with a text value in this column, that is no problem. So, the ODBC connection generates a sql insert statement that is mallformed in case of a long text. I have this problem consistent on all apps and all tables where i have NVARCHAR(>255). My solution is to go back to office release 2508 (semi annual support).Solved485Views1like2CommentsSQL Query editing UI issue
Hi everyone. For a couple of weeks now, my Access hasn't let me edit queries within the SQL option. Version: Access 2604 (Build 19929.20090) Basically, when I access the SQL View, I see the SQL code but can't select it or move the cursor to easily edit the text. It's difficult to explain, but I hope the following video helps: https://drive.google.com/file/d/1knAAwVS48m8WsarmhLeOVFWOdFuCqaUz/view?usp=sharing I've already tried restoring and resetting the installation, but to no avail. I hope you can help. Bets Regards, Emiliano76Views0likes4CommentsBold Duplicates (Conditional Formatting)
Hello experts I have a form based on qryLCAmends I want to bold the [LCNo] if there is a duplicate but ONLY where LCID = LCID here is what I have but it doesnt bold anything: DCount("*","qryLCAmends","[LCID]=" & [LCID] & "[LCNo]='" & [LCNo] & "'")>1 LCNo is text. I am using the "expression" in conditional formatting: Example: How can I do this with conditional formatting?Solved102Views0likes6CommentsMove Existing Sharepoint Linked Database to a different Sharepoint Site
Hi. I have a Sharepoint Linked Database that is working well within our company. We would like to use it within another subsidiary company that operates with its own Name and Sharepoint sites. Could you please assist as i am struggling to do this. ThanksSolved131Views0likes7Comments