access
1982 TopicsGive your Access forms a fresh look with rounded corners
Access is introducing a new Corner Radius property for form controls. You can use it to replace sharp square corners with anything from a subtle curve to a fully rounded outline - without custom drawing code or complicated workarounds. SCREENSHOT 1 - Before and after How it works Open a form in Design View, select a supported control, and find Corner Radius in the property sheet. The property accepts a non-negative whole number: 0 keeps the existing square corners. A value such as 4 or 6 adds a subtle curve. A value such as 8, 12, or 16 creates a more prominent rounded shape. Very large values make the control as round as its current size allows. The stored value does not change when you resize the control. Access calculates the largest radius that fits while preserving the control's existing content area. Set Special Effect to Flat for the rounded border to appear. Supported form controls The expanded feature supports these form controls: Text boxes Combo boxes List boxes Option groups Rectangles Labels Image controls Modern charts Attachment controls Subform controls For combo boxes, the control and its drop-down button use the selected radius. Command buttons and toggle buttons have long offered rounded corners through the Shape Type property. In future builds, Corner Radius will let you choose how much those corners curve, so you can match a button to the text box next to it. Lines, check boxes, option buttons, tab controls, and tab pages do not use Corner Radius in this release. This rollout applies to controls on forms; report controls are not included yet, but will be in a future update. Example: Refresh a customer details form You can use one consistent radius throughout a form, or vary it to create a visual hierarchy: Form element Suggested Corner Radius Text boxes and combo boxes 6 Grouping rectangles 12 Attachment and image controls 10 Modern charts 12 Start with smaller values and preview the form as a whole. A consistent radius usually produces a cleaner result than giving every control a different shape. Set Corner Radius with VBA Corner Radius is also available through the control's Properties collection: Me!txtCustomerName.Properties("CornerRadius") = 8 Use the Properties("CornerRadius") form in this release; direct early-bound .CornerRadius syntax is not included yet. Designed to preserve existing forms Existing forms keep their current appearance because Corner Radius defaults to 0. When you choose a nonzero value: The setting is saved with the form and retained when the control is copied. Rounded controls appear in Design View, Form View, Print Preview, and printed output. The control's content area remains rectangular, so text and other content do not lose space. To preserve that content area, a highly rounded border can extend slightly beyond the control's original rectangle. Leave a little extra space between tightly packed controls when using larger values. Try it Open a form in Design View. Select a supported control. Set Special Effect to Flat. Set Corner Radius to 8. Switch to Form View and adjust the value until the form has the look you want. Try the same value on several controls to quickly give an existing form a more consistent, modern appearance. Availability You can now set Corner Radius on all ten form controls listed above in these builds of Access for Microsoft 365: Beta Channel: Version 2612 (Build 16.0.20715.20004) Current Channel (Preview): Version 2611 (Build 16.0.20625.20102)90Views1like2CommentsDeprecation of Legacy Web Browser Control
We are announcing the planned deprecation of the legacy, Internet Explorer-based Web Browser Control in Microsoft Access, targeted for May 18, 2027, with version 2705. For Access LTSC 2024, the change is planned for May 11. If your Access applications contain forms that use the legacy control, we recommend migrating those controls to the Edge Browser Control before the target deprecation date. This post explains how to identify affected forms, convert existing controls, and prepare your applications for the transition. Why we are making this change Microsoft retired the Internet Explorer 11 desktop application and ended its support on certain versions of Windows 10 on June 15, 2022, as explained in the Internet Explorer 11 desktop app retirement FAQ. (techcommunity.microsoft.com) As part of Access’s continued modernization, we are now planning to deprecate the legacy, Internet Explorer-based Web Browser Control. We recommend migrating affected forms to the Edge Browser Control. (Use the Edge browser control on a form) Moving your forms to the Edge Browser Control prepares your applications for the transition announced in this post. What deprecation means for your applications When this change takes effect in your version of Access, legacy Web Browser Controls will no longer load or display web content. We will provide an option under Access Options to automatically load them as Edge Browser Controls, but this will not be the default. To preserve your application’s browser functionality, update the affected forms, review any associated VBA code, and test the updated application before deploying it to users. Who should take action? Review your Access applications if they include forms containing the legacy Web Browser Control. Include databases maintained by your organization, external developers, or solution providers. Forms that already use the Edge Browser Control do not need their browser controls converted as part of this migration. We recommend starting your review early so you have time to make changes, test your application’s workflows, and distribute updated forms to your users. For new forms that need to display web content, choose the Edge Browser Control rather than adding a new dependency on the legacy control. Identify affected forms Identifying affected controls is currently a manual process: Open each form in Design View. Inspect the form for legacy Web Browser Controls, distinguishing them from Edge Browser Controls. Note each control that needs conversion. Include forms used as subforms in your review. Repeat this process for each database you maintain. Allow time to convert the controls, update related code, test your application’s workflows, and distribute the updated database. Convert an existing legacy Web Browser Control to the Edge Browser Control You can convert an existing legacy Web Browser Control directly from your form’s Design View: Back up your database. Make and retain a backup before modifying your forms. Open the form in Design View. In the Navigation Pane, right-click the affected form and select Design View. Select the legacy Web Browser Control on the form. Convert the control. Right-click it, point to Change To, and select New browser control. Save and test the form. Open it in Form View and verify that the converted control behaves as expected. Repeat these steps for each legacy Web Browser Control in the forms you plan to migrate. Review compatibility and test your forms Treat conversion as the beginning of validation—not the end. Before deploying an updated database, we recommend testing: VBA, DOM access, and events: The Edge Browser Control does not expose the legacy control’s Object property or MSHTML object model. Code that directly accesses the HTML document or DOM through those interfaces must be rewritten. Use ExecuteJavascript to run JavaScript in the page and RetrieveJavascriptValue to retrieve the value of a JavaScript expression. Review related event handlers as well. Internet Explorer compatibility: Test websites and content that depend on Internet Explorer-specific behavior. They may require changes to work with Edge. Authentication and navigation: Test sign-in flows, protected content, links, redirects, and URLs that change with the current record. Review the Trusted Domains configuration where necessary. Local content: Test local files and review the Edge Browser Control’s local-file navigation requirements. User environments: Validate the updated forms in the Access environments where your application will run. For configuration guidance, including Trusted Domains and local-file navigation, see Use the Edge browser control on a form. Developers should also review the Edge Browser Control object reference when updating browser-related VBA code. (EdgeBrowserControl Object) Start preparing now The planned deprecation date is May 18, 2027, with version 2705. Begin identifying affected forms and testing their conversion to the Edge Browser Control now, allowing time to resolve compatibility issues before deploying your updated application.1.9KViews0likes3CommentsHelp Desk Sent Me Here...Help!
I'm getting the msg in a ribbon at the top of my excel files as follows: COULDN'T VERIFY SUBSCRIPTION Excel couldn't verify your Microsoft 365 subscription. Please make sure that you're connected to the Internet. ( I am ). we've rebooted several times, uninstalled, reinstalled etc. I can open all my excel files, but can't edit or save them. All dropdowns are "grayed" out. Microsoft Help Desk sent me here.305Views0likes2CommentsNew Zoom Feature allways removes like it's never been
Hi everybody, Ever since the zoom feature was introduced, I’ve repeatedly encountered a phenomenon where the feature—despite having been present—suddenly disappears. There is no slider, no zoom option in the ribbon, and no corresponding database options. I am using Microsoft® Access® for Microsoft 365 MSO (Version 2609, Build 16.0.20430.20032, 64-bit) on the Monthly Enterprise Channel. Following an update to this version, the feature reappeared. I opened several databases, and the slider was visible—it worked without any major issues (even though I rarely use it), with no crashes or error messages. Then, upon opening another database, the slider and all other elements related to the zoom feature vanished. When I went back to the previous databases, the feature had disappeared there as well. Restarting the PC and performing a "Quick Repair" had no effect. I have observed the same behavior across the previous five versions; the feature keeps disappearing. It seems that a new "Click-to-Run" update might re-enable it (though I’m not entirely certain). Something—or someone (Microsoft ?)—is disabling it. Fortunately, I haven’t incorporated this new feature into any of my objects or VBA code yet; otherwise, the database would crash! Does anyone have any ideas? Thx 4 reading501Views0likes19CommentsField disappears when zooming out below 100 Percent with mouse scrolling
Hallo Access-friends, Field disappears when zooming out below 100% with mouse scrolling (See screenshot) Continuous Form. The disappearance of individual fields seems to get worse the faster you scroll through the records with the mouse. If you use the right scrollbar, you don't have this problem or your zoom is 100 and higher. The problem shows up for me when you place a field with a transparent background over a conditionally formatted field. The error is reproducible; I can send a sample database. Another issue (maybe not new): I want a text box not to get focus (Here the big green Textbox ). Normally I do this by setting locked=true, enabled=false. But if the text box has conditional formatting, it can still get focus and then the field will be in foreground whats normal but not wanted. I use this construct for formating Records in contious Forms). The F1 Online description for Textbox-enable doesn’t seem right to me… or am I wrong about that? Hope this helps to make things better. Thanks for reading317Views0likes5CommentsExcel and word saving to invalid cloud location
There is a random account that belongs to my wife that keeps showing up randomly in my office 365. Supposedly last year it was "fixed", yet now suddenly it's showing up again when I create a new file in word. It says I need to sign in when I make it so I have to save a copy to my actual cloud to use it. This is driving me nuts, I need an actual solution, tried support and that was a joke. I'm on iPhone 15 pro max with iOS 27.2100Views0likes3CommentsFixes in Microsoft Access - Version 2610 (Build 16.0.20527.20088)
Known issue in the initial Version 2610 release Some databases may display an incorrect "There isn't enough memory or disk space" message when opening a report or exporting a report to PDF. A correction is planned for the next Version 2610 update. UPDATE: This issue is now fixed in build 16.0.20527.20112. Use 'Update Now' to update to the new build. Zoom Issue Fix Datasheet subforms did not zoom with Ctrl+mouse wheel Using Ctrl+mouse wheel over a subform displayed in Datasheet View now changes its zoom level as expected. Context menus appeared in the wrong location on zoomed forms Right-click menus now open at the selected location regardless of the form's zoom level, including near the lower-right edge of the form. A form divider line could stop halfway across at 50% zoom The divider between form sections now spans the full form width at 50% zoom and other supported zoom levels. Rapid Ctrl+mouse-wheel input could jump from 10% to 1000% zoom Zooming out quickly now stops at the 10% minimum instead of wrapping to the maximum zoom level. Big Forms Issue Fix Horizontal scrolling could snap very wide forms back to the left Design View and Form View can now scroll to controls positioned far to the right without the form unexpectedly returning to its left edge. Text formatting remained limited to 22 inches in wider controls Text can now be formatted and displayed across the full width of fixed-size text controls wider than the former 22-inch form limit. Forms and controls Issue Fix ControlTip text could remain visible after typing began ControlTips now close when keyboard input begins, preventing the tip from covering the form during data entry. Property Sheet text could become unreadable after changing the Office theme The Property Sheet now refreshes both its foreground and background colors immediately after a theme change, without requiring Access to be restarted. Queries and data Issue Fix Bracketed object and control names could occasionally be read incorrectly Access now reliably preserves a name when removing its surrounding brackets. Stability Issue Fix Opening forms with grouped control layouts could cause Access to close unexpectedly Access no longer closes unexpectedly while determining the bounds of grouped layouts when affected forms open in Form View. Changing a subform's SourceObject could cause Access to close unexpectedly Changing a subform's source from VBA during an event now completes without causing Access to close unexpectedly.1.5KViews3likes5CommentsOffice 2019 for Mac – Perpetual License No Longer Activates
Hello, I purchased a genuine Microsoft Office Home & Business 2019 for Mac perpetual license in 2024. The product was successfully activated and is still registered to my Microsoft account. Until recently, everything worked perfectly. However, Word (version 16.113.2) now refuses to activate and displays a message stating that my Office 2019 license is no longer supported. I understand that Microsoft has ended support for Office 2019, but I purchased a perpetual license, not a subscription, and I would like to continue using the software I paid for. I have already contacted Microsoft Support, and they referred me to this community. Could someone from Microsoft please advise how I can restore my existing license? If this is no longer technically possible, I would appreciate an alternative solution, such as a complimentary upgrade to a compatible Office version. I would prefer not to purchase another license simply because my previously working software can no longer be activated. Thank you for your assistance.213Views0likes2CommentsMS Access ODBC driver doesn't support SQLPrimaryKeys function
I'm writing a python script using pyodbc to read an MS Access database. I was hoping to read the primary key of each table, but I'm getting the error IM001 "Driver does not support this function (0) (SQLPrimaryKeys)". Is there another way I can check the primary keys with python?218Views0likes1Comment