Search results

To question #1: My experience has taught me to always create an ACCDE with the oldest required Access version. There was always trouble the other way around. But I have to admit that I haven't tested how it currently behaves for an estimated 10 years... To question #2+3: Unfortunately, I can't...

Now we know where the AIs get their knowledge from... :ROFLMAO: ;)

'Decompile/Compact' the accdb first can help too.

You are passing your criteria to the parameter 'WindowMode' of 'OpenReport'. So check the commas.

Asked by the same user... ;)

Hi Philipp, unfortunately there seems to be no built-in indicator/constant in conditional formatting syntax representing the row to be formatted. But if you could provide a column with an ascending number somehow in your forms recordsource, then you could use this approach. Given a column...

And in the next stage of programmer enlightenment, you also remember how to fix it... :cool:

What does it look like when you use a Runtime locally on a client? Maybe it's the runtime in general? Have you compared the patch level (Microsoft Access version/build) of your Access full version with that of the runtime used?

Private Const FLASHW_STOP = 0 'Stop flashing. The system restores the window to its original state. Private Const FLASHW_CAPTION = &H1 'Flash the window caption. Private Const FLASHW_TRAY = &H2 'Flash the taskbar button. Private Const FLASHW_ALL = (FLASHW_CAPTION Or FLASHW_TRAY) 'Flash both the...

Thanks for the answer, I compile and save too often rather than too little and do not have the problem described. But for the back of my mind, I'm interested to know if there is any insight into the setting mentioned.

Have you received any further information on this setting? How were your trials?

Thanks @Josef P. , thats annoying.

It looks like my suggestion has been completely deleted. Thank you Microsoft.

Forgot to post the link: https://feedbackportal.microsoft.com/feedback/idea/051eedaa-5068-ef11-a4e6-000d3a02a3a1

Done. But we all should do that, or second my request. ;)

Maybe the Access team would add a procedure like 'ClearCredentialCache'?

Your table has no primary key?

This could have been written by me... :) (y)

Perhaps you have decompiled and compacted your database file in the meantime? This cleans up some stuff. It wouldn't be the first time this has been a cure for fancy problems.

It's hard to follow your explanations just mentally, but what immediately popped into my head was whether you might have created circular references of two or more objects that prevent each other from being deleted by the garbage collection...