Search results

I have discussed the questions raised in this thread at some length with several current and former MVPs, all of whom stated that the behaviour I described in post #4 is exactly what they would expect. In summary, the consensus from those MVPs was that: A signed project indicates one that has...

There is one problem you may have in solving this. Because popup forms are 'above' the application interface, they are never considered as the active form by Access and cannot be referenced as such. This may make it harder to handle your issue with code

LOL! I've forwarded a link to this thread together with my entire reply to the A-team and sincerely hope it will trigger a response from them as well. As I wrote in that email Although its still incorrect, I'm less bothered by the fact that a project without errors remained signed after it...

I'm intending to mention the point in the EDIT to the Access team

As @Gasman said, its very easy to test this sort of question yourself. Using an .ACCDR file is equivalent to using the /runtime switch In both cases, the shift bypass was ignored

@AHeyne That's an interesting question that I hadn't considered before and was easy to test! First of all, signing a compiled project does not cause it to become decompiled. I tested signing a decompiled project both from within Access and using the new command line signing option. In both...

API declarations will compile in 64-bit if they include PtrSafe. However, that doesn't mean that they will work correctly in that bitness. Thorough testing is essential To the best of my knowledge, all Office licenses from at least 2010 onwards allow users to install Office on at least two...

A few years ago, I wrote a lengthy article about 6 different methods for measuring time intervals including a high resolution timer capable of measuring to 0.1 microsecond precision. Unfortunately, its accuracy is less than many other methods. For full details, see my article which includes an...

Apart from the unnecessary use of Win64, I'm surprised if it worked when the output was wrongly defined as LongPtr.

I haven't yet had a chance to look at your book but I disagree completely with the conditional compilation in post #22 by @moke123 #If VBA7 works for any 32-bit or 64-bit in A2010 or later (VBA7) The #Else part is only needed for VBA6 i.e. A2007 or earlier In addition, the output should be...

Its ancient code but .... https://isladogs.co.uk/logged-in-users/index.html

Focusing on your final paragraph… Popup forms are displayed where they were last saved in design view. So if you saved them on a secondary monitor, that’s where they will reopen. If then opened on a workstation with only one monitor, they will indeed be off screen. Suggest you reopen the...

There is a fundamental difference. Edgar's code works whereas using DoCmd.SetWarnings False doesn't have any effect in this context

Obviously not a bug. As to whether it’s beneficial will depend on circumstances. For example, I had a report of well over 1000 pages which takes a very long time to print to PDF and can cause Access to hang. In such cases, being able to cancel is a necessity

Hi George No need to apologise. John and I have been in contact. I have a link to his book but not yet found time to look at it.

Just tried the above example app supplied by @Edgar_ I altered the somePath line to match my desktop location as I was getting error 2501 when the PDF was completed 1. For initial testing I ran the code as supplied. The Printing dialog appears as normal and the PDF is created after just over...

Hi John Welcome to AWF. For those who don't know, John has been a regular presenter at the Pacific chapter of Access User Groups which is led by @GPGeorge. John's next presentation for that group is on Thur 5 June...

I haven’t yet tested Edgar’s code but from his comments it appears I was wrong and that the message can be suppressed, albeit with an undesirable side effect. If that can be overcome, then I’m all for it!

One of the many advantages of maintaining one version and restricting according to e.g. job role or license type is that the app doesn’t need to be reinstalled if the conditions change e.g changing job role or purchasing a Pro license. It will update the functionality automatically according to...

@Eugene-LS In what way is your code safer in your opinion?