office 365
400 TopicsMsgbox or Modal window Crash on PC Sleep
This has been an issue for a couple of years, but I haven't spent too much time trying to solve it because I thought it would eventually go away. It hasn't and it is becoming worse as I develop other parts of my application. Situation: When a msgbox (or modal window) is open and the PC sleeps, the application hangs upon PC awake. There's no way to get out it with ending the process. To replicate: Create and save blank database Create one module with a single public test function Enter msgbox "Hang Test", vbOkOnly Hit F5 to run the code. The message box pops up. Leave it. Put PC to sleep manually with windows | power | sleep Awaken PC, Access is now frozen. GPT provides a lot of explanations for this behavior, but it doesn't make sense and must be something that can be addressed. Windows 11, Version 2606 (Build 20131.20126 Click-to-Run)26Views0likes1CommentAccess 365 Issues
I’m running Windows 11 pro, dual monitors (200% laptop and 100% external). Quick repair did not work. Issue 1: When I open Access 365, the navigation bar is only about and inch wide. I can close it, but it only opens to an inch wide. How do I fix this. Issue 2: I opened the Contact template in Access then save copy. I want to customize the saved copy. The copy seems to be locked. I can’t make any edits like add fields and unfreeze pane. How can I edit copies of the templates include in my Access 365?24Views0likes1CommentPOWER POINT Y COPILOT
Estoy haciendo una presentación en Power Point con Copilot. Durante un rato le di ordenes de buscar fotos y subirlas en tales o cuales diapositivas y lo hizo sin problema. En un momento dado dejó de hacerlo, me dijo que había una falla generalizada en el sistema y dejó de hacerlo. En el chat de asistencia de Microsoft me dijeron que tal vez era un tema de límite de uso de IA y que tenía que pagar Premium. Lo hice y todo sigue igual desde hace 5 días. Hoy estuve 3 horas chateando con un técnico, me hizo desinstalar apps y volver a instalar pero no pasa nada. Es increíble que una IA no pueda hacer algo tan simple como buscar una fotografía e insertarla en una diapositiva. En un momento Copilot me contestó: yo sólo te puedo decir cómo hacerlo, pero no hacerlo... Increíble para una IA!48Views0likes2CommentsAccess VBA performance dramatically slowed since June Update
We are running an access based application with a large vba project. One customer with four different instances of this project experience extreme slow down in performance on all instances during the last week. We made no changes. The Microsoft Office Update was applied automatically. We believe the problem happened then. We have tried reverting to several different previous versions of Office but symptoms still remain.363Views0likes7CommentsText Truncation in Access Report Controls
Around May 14, 2026, we began experiencing text truncation on the right side of text box controls in Access (Office 365) reports. Approximately 2–4 characters are cut off whenever font size is below 10pt. All reports in our environment are affected and the problem was not present prior to May 14. We ruled out layout as a contributing factor by verifying page size, margins, report width, control dimensions, padding, and layering were all correctly set. No layout changes resolved the issue. The problem does not occur when font size is set to 10pt or higher, suggesting the update affected font metric calculations for small font sizes. Steps taken without resolution include adjusting all report and control sizing properties, testing multiple default printer configurations including Microsoft Print to PDF and Adobe PDF, and verifying Windows display scaling was set to 100%. If anyone has any solutions, please let me know! Thank you for your time.58Views0likes1CommentRegression in v2605: Subform with overlapping controls breaks timer in unrelated form
I found another issue (sorry) which might be caused by the zoom-related changes in 2605. The following repro example works fine in 2604 (Monthly Enterprise Channel) but breaks in 2605 (Current Channel). Again, this issue is unrelated to zooming itself. Prepare database The repro requires three forms and a few controls. Since those are tedious to get right manually, I wrote some VBA code to do that for us. Execute BuildRepro() in the Immediate Window to create the forms and controls. Option Compare Database Option Explicit Public Sub BuildRepro() CreateFormASubform CreateFormA CreateFormB End Sub Private Sub CreateFormASubform() Dim frm As Form Dim ctl As Control Set frm = CreateForm() Set ctl = CreateControl(frm.Name, acTextBox, acDetail, , , 345, 1140, 1746, 260) ctl.TabStop = False Const textBoxTop = 260 Set ctl = CreateControl(frm.Name, acTextBox, acDetail, , , 56, textBoxTop, 270, 270) ctl.TabStop = False Set ctl = CreateControl(frm.Name, acImage, acDetail, , , 56, 0, 270, 270) Set ctl = CreateControl(frm.Name, acCommandButton, acDetail, , , 60, 795, 5895, 260) SaveAndClose frm, "FormA_Subform" End Sub Private Sub CreateFormA() Dim frm As Form Dim ctl As Control Set frm = CreateForm() Set ctl = CreateControl(frm.Name, acSubform, acDetail, , , 100, 100, 3000, 3000) ctl.SourceObject = "FormA_Subform" SaveAndClose frm, "FormA" End Sub Private Sub CreateFormB() Dim frm As Form Dim ctl As Control Set frm = CreateForm() frm.TimerInterval = 1 Set ctl = CreateControl(frm.Name, acLabel, acDetail, , , 100, 100, 5000, 1000) ctl.Name = "my_label" ctl.Caption = "Waiting for Timer..." frm.HasModule = True frm.Module.InsertText _ "Private Sub Form_Timer()" & vbCrLf & _ " Me.TimerInterval = 0" & vbCrLf & _ " Me.my_label.Caption = ""Done""" & vbCrLf & _ "End Sub" frm.OnTimer = "[Event Procedure]" SaveAndClose frm, "FormB" End Sub Private Sub SaveAndClose(ByVal frm As Form, ByVal newname As String) Dim oldname As String oldname = frm.Name DoCmd.Save acForm, oldname DoCmd.Close acForm, oldname DoCmd.Rename newname, acForm, oldname End Sub Run repro 1. Open FormA. 2. Open FormB (while FormA is still open). Expected result: FormB opens completely, the timer runs and the label reads "Done". Actual result: FormB opens "halfway" (it's visible, but it's tab is still missing, see screenshot below) and the label still shows "Waiting for Timer...". As soon as you right-click anywhere, the form finishes opening and the timer runs, changing the label to "Done". Notes: I tried to make the repro as simple as possible. If you remove one of the controls from FormA_Subform (or enable TabStops), the problem disappears. It might have something to do with overlapping controls: If you change textBoxTop from 260 to 280, so that it no longer overlaps with the image, the problem also disappears. We need the overlapping controls because in our real code the subform is continuous and displays data at different indentation levels (like a treeview).209Views0likes6CommentsTab header font issue when the "new zoom" feature is enabled
We found a curious font display issue, which can only be reproduced if the "new zoom" feature flag is active: We can reproduce it with build 20026.20076 with the zoom slider visible (e.g. in the "Current Channel (Preview)"), but we cannot reproduce it on the same build with the zoom slider invisible (e.g. on a freshly updated system in the Current Channel, which has not received the staged rollout yet) or with older builds (e.g. the current Monthly Channel build). The problem itself is unrelated to zooming. Repro 1. Create a new Access database. 2. Create a new form in Design View. 3. Add a Tab Control. 4. Set the tab control's "Use Theme" property to "No". 5. Add a button with the following code: Private Sub Command3_Click() Dim start As Double ' Localize the page name, if you use a non-English version of Access Me.Page2.Visible = True ' Simulate long-running operation (3 seconds) start = Timer Do Until Timer > start + 3: Loop End Sub 6. Save and open the form in Form View. 7. Click the button. Expected result: Nothing happens for 3 seconds. Actual result: The tab header's font switches to some old raster system font (MS Sans Serif?). After 3 seconds, the form returns to the 21st century. This issue is easy to work around: just do the long-running operation before setting the Visibility property, this will reduce the font-change to a short flicker. Still, this appears to be an unintended side effect of the changes made for the "new zoom" feature, so I thought it might be helpful to report it while that feature is still being worked on.Solved92Views0likes2CommentsHow do I get support with Authentication when it doesn't work?
I have a business 365 account but changed address and so my credit card payments stopped. However, I can't log in to my account because I have an authentication problem (my authentication app on iPhone is still working but the entry for this account has gone and there is a new one called "Microsoft Entra ID" but when I go to get the authentication code this "Entra ID" authenticator does not produce it). To get help from Microsoft it always asks for authentication. I would like to keep this account and start paying again but I can't find a way to get help to fix the authentication problem because raising a ticket or talking to an agent requires authentication.121Views0likes3CommentsODBC 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).Solved549Views1like2Comments