Recent content by sonic8

Here is a crude approach that I find much more comprehensible than Copilot's suggestion: Public Function IsLargeInteger(ByVal varValue As Variant) As Boolean If IsNumeric(varValue) Then If CDec(varValue) >= CDec("-9223372036854775808") _ And CDec(varValue) <=...

Because the OP has in VBScript in use already, and the conversion can be done in seconds while the deprecation will take several years.

It is, but can be converted to VBscript with minimal effort.

*Reading* HKLM is not a problem for non-admin users.

If you prefer a script over an Access app, you should look into Powershell.

Yes. I think, you just need to use the full path to MsAccess.exe and it should then also work with the runtime. PS: Keep in mind that VB Script is deprecated and will be removed from future versions of Windows.

Very good. You might need to count either distinct user or distinct remote PID because one Access frontend might use more than one connection.

I'm not familiar with Firebird but a quick look into the docs shows that it is possible to create a database trigger for the CONNECT event. That should allow you to implement my suggestion although you need to work out the details yourself.

You are using SQL Server? Then use a LogOn-Trigger to count the connections grouped by either user or computer name.

So, essentially, your old code still works but (some) new code causes errors? The simple explanation would be that you made errors writing the new code. If you don't think, after thorough review, that this is the case, you should post the code in question.

This sentence is misleading. It should read: "Now the default is to block such queries if the registry key does not exist."

This is good advice. - In theory. In practice however, ... - There is no AD and the client has no desire to get one. - There is not even a network connection from the outside into their local branches, where most of the users are. In general, the client is not very fond of Microsoft and its...

That's a good idea. I didn't yet. I will do so, but I might not have an opportunity until next year. (Users work in a retail shop scenario and at this time of the year they are too busy to allow me to remote into their computers.)

I now implemented a rather crude workaround... I daisy chained multiple approaches to send the email one after the other. 1. I try DoCmd.SendObject, which at least works on some computers. 2. I use arnelgp's Thunderbird command line approach, which surprisingly even works with very long...

I did this already; forgot to mention it. They all have Thunderbird set as Default Email App. (There is no other email app installed.) This settings appears to have little effect. On the one computer where it now works this was set initially, but sending emails with DoCmd.SendObject still...