Search results

But then with a salt that none of the participants knows, otherwise they could try to create and compare hashes themselves using the names involved...

Happy Star Wars Day! 😉

Maybe the automatically started process runs as a different user or with different privilleges?

The concepts presented in your links are very interesting. Your last sentence in particular tempts me to ask you whether you have any examples of how you have implemented something in Access. Can you show us something, possibly just screenshots?

I particularly appreciate the width of the display in the Immediate Window. The expressions you enter there can be quite a bit longer.

Just out of interest, @Gasman : Which update channel does your Office 2019 installation belong to? And is it of installation type MSI or C2R?

Of course, this is just a guess. But I've learned to think a little more broadly when troubleshooting when you're stuck. ;-)

Should be I would say. I've seen misconfiguration in Windows caused by whatsoever, where the domain status of the network was gone.

Yes, but maybe this first option is disabled on some of his PCs because of the network settings. Maybe there is a rule to not allow this on public networks. It's just an idea.

Maybe it depends on the specified type of network of your NIC (public, private, domain)?

Ah, ok, you're right.

@isladogs : If you could make a snapshot of your VM you could easily check if Access 2003 still works properly after upgrading to SP3 or also to 11.8321.8405. That would at least end this long thread with a conclusion, I think. ;-)

Build 11.8321.8405 is even newer than SP3. It represents the latest version known to me. Interesting would be now, which build @isladogs has, because on his pc it is running well he wrote in #34.

Is it only running on the unpatched computer? Funny. You could do a cross-check and install the updates on the computer where it is running. :p

One more: As you say you have two Windows 10 pcs with Access 2003 where only of them has the described problem. Did you compare the Access version on both computers? Are they different? Especially the part "(11.8321.8405) SP3" like in the sample screenshot should be compared:

Ok, I'll try again. The version/patch level of the Access 2003 version you have now installed may be older than the service packs/updates released by Microsoft at that time. You could therefore use these 'old' service packs / updates to upgrade your installed Access/Office to a newer version...

I am well aware of this, I also got rid of Access 2003 when it was time... Nevertheless, it is possible that your Office/Access setup is older than the latest service packs and patches provided by Microsoft at the time, especially now that you have reinstalled it. Have a look here (SP3)...

Maybe there are updates and/or service packs for Office/Access 2003 available, which are not installed, and maybe fix the behaviour?

Maybe it is in a wrong position because of some display metrics? Do you have a different monitor or resolution as before? Or did you change the scaling? Or did you use a second monitor in the last time and now it isn't connected any more? Just guessing because it seems to be so weird...

@arnelgp : Out of curiosity, where did you get this information ("while your SQL Server can have 255 connections") from? I would like to read it's context.