Search results

Why should it be public? Lebans wrote it as private and it has been working that way without a hitch for at least fifteen years. In any case, I just tried making it so, and no difference - still crashes. And I am trying very hard to track down all the instances of data types, but nothing yet...

Ah, thank you. It is, though - it's the very next routine after this AutoShutDown. Private Sub TimerProc(ByVal hWnd As Long, ByVal uMsg As Long, ByVal idEvent As Long, ByVal dwTime As Long) ShutDownGDIP End Sub One of the things I've tried is changing the parameters here to LongPtr and...

If you mean this: tVarTimer(lCounter) = SetTimer(0&, 0&, 5000, AddressOf TimerProc)then that is is a regular module. I don't know what a static class would be.

Yes, I suspect it is that. I've put in conditional compilations for 64, but no luck yet. It's hard to work on, because every failed attempt crashes the app, and it's kind of a pig to start. Some of the code is in a class module, some in a regular.

I have several apps making use of Lebans' picture box class. They have worked great for many years, but they have started bombing as users have switched to 64-bit systems. I've tracked it down to the following code, which run great on 32-bit machines and causes Access to shut down on 64-bit...

The error is when I open that subform, or any one of several similar forms. The query itself works fine, as do all the queries for all such forms.

.ZIP

Even almost emptied and zipped, it's almost 20 MB. Don't know what the limit is in this forum, but that exceeds it. It is available to download on a large file transfer site: https://www.uschovna.cz/zasilka/OXW8ZK4BDKLW429B-JXX

Thank you, I tried that. Same thing - it throws the error and never executes the code.

I just tried making a copy of one of the datasheet subforms, and starting it alone. If I clear out ALL the event calls, it opens normally, in all three modes: datasheet view, single-record view and continuous view. If I have ANY event code links, it throws the error, and after I click away the...

I also just now removed the table that has some images for the ribbon, and the only table in the entire DB that has OLE fields. C & R after removal. No change.

Ribbon table completely removed. No change. But in the process, I discovered something else odd - starting the app with Shift does NOT start it the way I would expect - side panel visible and start code not executed. It still insists on trying to start the start-up form. And of course, still...

Okay. At this point, I'm willing to try anything. I'll post back what happens.

They do not. I am very careful to avoid ALL such names, everywhere. Strictly US A-Za-z, numbers and underscores. No spaces, no special characters, no foreign characters. The only place I use non-English characters is comments, and label or field captions on forms and reports. And of course, I...

Update - the user bought Office 365 and tried installing it - same error. Now I'm completely confused. It appears that something is well and truly effed in the machine as a whole, since three different version of Access throw the same error, in an app that works perfectly everywhere else. But I...

The actual .ACCDB file is not the one that I tried in 2019. The user brought over a fresh copy from his other machine, which still has 2007 and where it all works normally. I never tried opening a version in 2007 that had previously been opened in 2019. I can look in the trash, if you think that...

I'm not sure what you mean by package. Do you mean the database? It opens normally, both previously in the 2019 version and now in 2007, and messing with it does not show any oddities that I can discern. It compiles, the immediate window runs expressions properly, the VBA editor works, the forms...

Just got hold of the customer. The installation is the entire Office package. He cleared out the 2019 installation and put in the entire 2007 bundle, which throws the same error as the 2019 version.

Yeah, I didn't bother formatting it because there is nothing in it I wanted anyone to try troubleshooting. Just showing that there is nothing exotic in it - a vanilla-grade Select with some Joins and a bit of formatting. And it works perfectly. I can try importing only the minimum of tables...

The source query is an ordinary Select statement, and works fine on its own. It is non-updateable, but that is intentional. And numerous other forms in the DB throw the same error when I launch them by hand. Normally, they are all called from the ribbon, or an occasional button on a form, but...