Search results

I doubt it will be a problem installing it even with an older version such as 2010. Activation might be an issue though.

No need to uninstall. Your friend should be able to install Office on at least 2 PCs with the same license. If its a recent version, he can go online and de-assign (is that a word) the Office install on the old machine

Perhaps time to consider updating to a newer version.

The constants are listed here this MS article: https://learn.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-showwindow SW_SHOWMINIMIZED=2 SW_MINIMIZE = 6 EDIT: @LarryE has the full list already

Perhaps Tom was too subtle OR perhaps not 😊

The code also works for me in both A365 v2512 and A2010 v14.0.7268.5000 As Tom said, decompile to hopefully fix likely corruption. (EDIT - too late) Next try reinstalling Office 2010 Even though the code casts string response correctly as integer, I also see no reason why you would have used...

Option 7 works for me but not option 2 EDIT: Retested using Excel, Word & PowerPoint. In each case, both options open the app minimized to the taskbar. Outlook is the exception.

Just tested in A2007. After fixing 2 missing references, unfortunately the WIA code doesn't work in that version. It will work if you can update to a newer version from A2010 onwards

The video of Ynte Jan's masterclass presentation to the Access Europe User Group on 5 Nov is now available on YouTube . Watch, learn and enjoy.

Please show a screenshot when image F2 is selected - same as my screenshot in post #10. Also can you confirm your Access version, build, update channel, bitness and Office language as this info may be relevant. I think you are using Access 2007 32-bit English. My example app is only guaranteed...

The first image F1 is correctly orientated. Have you tried the others e.g. F2 is flipped horizontally and the app also displays a corrected version Similarly F3 is rotated through 180 degrees, F4 is flipped vertically etc . . Did you look at the other images as well?.

Seems to be fixed now

Juanjo Luna did an Access Europe session on Blazor back in 2023: In addition, John Heaser did a session on Blazor for UKAUG around the same time. It was recorded but the video is only available to members

@Jason Lee Hayes I would like to download v2.52 and 2.53 for testing, but unless I'm being very dense, you haven't uploaded the files here (screenshots only)

I have had the same error twice today when searching for messages by a specified member

Thank you. I can replicate that in A365 Version 2512 Build 19504.20000 Beta 64-bit and have informed the Access team. I suspect that the hidden window is used by the Monaco speedy loading feature. UPDATE I got a response from the Access team within a few hours. The issue is being investigated

@Dave_D Welcome to the forum. Yours is now the third report of this bug which so far I have been unable to replicate. Does it only happen with one Access front end or with several? Does it only happen with a SQL Server BE? What is your Access version, build, update channel and bitness? i am...

@Albert D. Kallal You're welcome. I enjoyed revisiting old versions of Access back to 1.0 for the purpose of the article. Some of the early versions I hadn't looked at in many years. I totally agree with you about the top three Access versions being 97, 2003 and 2010 with the two worst...

There is almost no documentation about this so I wrote an article on the topic a couple of months ago: https://www.isladogs.co.uk/windowed-controls/index.html As you mentioned most Access controls are non-windowed and only get a windows handle when they have focus. The exceptions are windowed...

@JohnC1939 What is this change in Monaco query SQL view that you are referring to? Can you provide a simple repro database that shows the unhide window problem?