Search results

Fantastick PUN Doc_Man! BTW: My problem has at long last been solved. I failed to get back here and post soon enough to rememebr the details, but I will do the best I can from memory. I wrote a tiny C# app that runs on Windows start-up. It asks for a different password and if correct it...

Hey THE_DOC_MAN... Did you notice in my previous post that I do indeed have those same events in the log for the 32 bit office machine as well as the Windows 11 (64 bit) Office machine, but - I NEVER see MS Access re-Launch on those two PCs? Also, during that 12 - 15 seconds my PC is perfectly...

OK here's the Latest: I searched through the event log on my 64 bit Windows 10 Pro PC that has 32 bit office installed. And, I did indeed find Event ID 1001 with MS Access App Crash reporting both CLR.DLL and COMBASE.dll. with the c0000005 value. There are a few of these over the past few...

The company that I am currently contracted to just updated their PCs to 64 bit Office (thinking that someday soon this would be the best/only option). That is the only reason that I switched to 64 bit on my new PC. So, I cannot switch back right away, but I will try to do so as an experiment...

OK. Just verified the following: Open one of my Access Applications with the shift key held down (this is my unlocked development copy). So, no code running, no forms open, etc.. Now, open a module, make a quick edit, do a debug-compile from the ribbon menu and then close the database...

OK, Let me clarify! I do know all about 32 bit versus 64 bit (PtrSafe, LongPtr, etc.). And, I have no 32 bit "machines" (boat anchors) in my stable. I do however have a 64 bit Window 10 Pro machine that has 32 bit Office installed and that is the PC that does not exhibit the issue. I also...

First of all, my apologies! I was busy for the last several days and have not had time to respond. So, please bare with me. Arnelgp, - I turned off DEP for everything (had to disable secure boot first) and the problem still occurred. THE_DOC_MAN Thanks you SOOooo much for your very...

Lately, this is what shows up in the Even Log: Fault bucket 1374643201473705203, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: MSACCESS.EXE P2: 16.0.14701.20262 P3: 61ba84b9 P4: clr.dll P5: 4.8.4420.0 P6: 6109cbc8 P7: c0000005 P8: 00000000001186f2 P9...

About ready to give up! I ran a better memory test on the new PC (the one with the issue) and it passed. Then, I took a close look at the even log on the other PC that has the identical version of office (but running Win 11 Pro instead of Win 10 pro). And, lo and behold there were several...

I’ve reinstalled 64 bit office. I’ve reinstalled Windows 10 pro. Ran sfc. Have all of the latest updates. Have the same exact version of Office/Access on a Windows 11 pc, and no problem with it. Have not had time to run a deep memory test, but that is next on my list. Any other ideas?

I am having an issue with a new Dell PC. It passes all of their on-line diagnostic tests so I am not sure that the PC is the issue. Basically, when I have almost any MS Access database open, and I dink around in the VBE (whether or not I make any changes) and then I close the VBE and later...

OldDBGuy here: Hi, my real name is Dan, and I am a very experienced MS Access developer. Been doing this since 1995. Have my own consulting/Contracting business for MS Access custom databases. And, sorry to say, will not have a lot of time to participate in this community. But, will do what I...