Search results

Double check that youhaven't also defined gbDebug in another module (as Private or Public) Duplicate declarations can cause problems.

Also have a look at my article: https://www.isladogs.co.uk/multivalued-fields/index.html For info, multiselect listboxes are not the same thing as multivalued fields

@GPGeorge Not sure which reference you copied. However, just to be clear, that incorrect comment about the Win64 compiler directive didn't come from my article that you linked in post #6. Thanks for adding the link however!

Better still, if all your users are on A2010 or later, remove the conditional compilation completely and just use: Public Declare PtrSafe Function apiGetWindowsDirectory Lib "kernel32" Alias "GetWindowsDirectoryA" _ (ByVal lpBuffer As String, ByVal nSize As Long) As Long Coming back to...

I can't see the issue you describe using your code (with the specified section commented out) No additional instances remain in Task Manager and Access doesn't hang for me. EDIT I tested in 365 version 2509 build 19220.20000 Beta 64-bit. It may be relevant as to which version build / bitness /...

Saying 'it didn't work' is of no help for anyone trying to troubleshoot. As already stated, if the Bestelbon field is text then you need single quotes as delimiters. You don't need the Bestelbon field in the SELECT clause sql = "SELECT Productnaam FROM Planning INNER JOIN Tanks" & _ " ON...

Back in 2016 or so, I decided to ‘future proof’ my application installations by adding 17.0 to the registry trusted location scripts that I circulated with my commercial and some free apps. I know some of my clients have 17.0 listed in the registry as a result. It does no harm but neither does...

Pat There has never been a version 17.0 for Office Every version from 2016 onwards including 365 is 16.0

That should be Database field in MSysObjects (not property). Similarly for the Connect field (not Connection property).

Just checking you were awake! 😙 Corrected above

Glad you have a solution. In answer to your questions in post #5, there is no inherent difference in centering (or otherwise positioning ) reports compared to forms. DoCmd.MoveSize is subject to the same integer twips limit of 32767 as for form and report widths. For MoveSize you need to set...

Glad it worked out for you. I knew it would once I saw those screenshots, which is why I pushed you to update.

Restarting is unlikely to help accelerate matters (assuming it recovers from the dead). Don’t be afraid of forcing the update in the way I described. It’s easy.

You’ll get that version eventually via an automatic update but it’s easy enough to do From backstage view, click Account | Update Options | Update Now. If the update is available to you the update process will start automatically

As the AFo article states in the first line, various 32-bit wizard related issues were triggered with version 2507 build 19029.20136 released on 30 July. Just run a version update in the usual way to get the latest current channel version.

Bingo! The information in post #24 was very helpful. Although you haven't said so, I think you may be running 32-bit Access 2016 version 2507. If so, you may be affected by a bug that affected various wizards See https://www.accessforever.org/post/wizard-activexs-are-broken-in-32-bit and...

OTOH, if your end users do not need to do things like add/alter query design then using the .accdr suffix does have advantages. For example, it automatically locks down the file, hiding both nav pane & ribbon from users without you needing to apply all security yourself using code. However...

If you look back at post #1, the VBE also displays an old and apparently redundant VB6 Components dialog box when Ctrl+T is pressed. Likewise, just because the items still exist for the Easter egg, it doesn’t mean that they can be used.

I had already tried both of those before posting Taking point 2: it is illogical to make your form / subform very tall, then reduce it to show the vertical scrollbar Just make the form shorter in the first place.

I tested in a 22 inch monitor earlier. However, it shouldn't make any difference what size monitor you have with popup forms