Search results

You've really put a lot of work into this. What you've found out sounds quite confusing (not from you, but in terms of the context). I think it all boils down to accepting that you can't figure everything out. I played around a little with the layout-related properties from my initial post...

Very nice. Works on 64-bit VBA well too! (y)

Thanks Tom, I will have to take a look at this.

As I said, I don't want to use a sledgehammer to find the Holy Grail or other artifacts, but rather encourage the community to introduce properties that haven't been mentioned here yet. At least that was my idea, which unfortunately was somewhat misunderstood (but I think I may have expressed...

@Edgar_ : Thank you for the information. But as I have already written here and added in my first post now, it's not specifically about compiling a complete list for the sake of it, but rather about gathering knowledge about such useful properties in one central location. So if anyone knows of...

Hi, no, I didn't ask him yet. I could actually do that, thanks for the suggestion. @Albert D. Kallal : Thank you for your detailed reply. While reading, I wondered when you would get to the point of this thread, but ultimately I feel that your post would be better suited to its own thread, as...

Perhaps I should have phrased that differently at the beginning. It's not specifically about compiling a complete list for the sake of it, but rather about gathering knowledge about such useful properties in one central location. I would have thought that uncovering the possibilities this...

You mean one would have to add it himself to be able to use it afterwards?

@ First: Sure, I could loop the collection, but how to check programatically which of them doesn't exist of a named property in the object model (e.g. in the object browser)? And if I really find some, there will be no explanation/description. @ Second: I don't quite follow what you mean. @...

In the video contained here (https://isladogs.co.uk/aeu-11/index.html), Karl Donaubauer addresses the topic of 'New Properties of Objects'. It deals with properties of various objects that cannot be addressed using "." syntax, but only using the "Properties" collection of the respective object...

@isladogs: Since you touched on the topic of ‘timeout’ in your article: In addition to the MessageBoxW API, there is a similar one with timeout: Private Declare PtrSafe Function MessageBoxTimeoutW Lib "user32.dll" (ByVal xHwnd As LongPtr, ByVal lpText As LongPtr, ByVal lpCaption As LongPtr...

What is the content of the constant/variable named "ODBC_DRIVER"? More ideas: Did you check the "SQL Server Configuration Manager" on your SQL Server? Take a look into "SQL Server Network Configuration", choose your SQL Server instance and ensure TCP/IP is activated. Then restart your SQL...

I did some more testing regarding the maximum text length, the wrapping of long lines without spaces, unicode and Ctrl-C support. Maybe it will be interesting/helpful for your article Colin. VBA Msgbox: - Displays max. 1023 characters - Wraps long lines, not containing blanks or similar -...

Very interesting, Colin! I wish the Access team would sort this out and document it accordingly. Because at the moment, no one knows exactly how long each 'technology' will be supported...

The command-query separation programming principle comes into play here. https://en.wikipedia.org/wiki/Command%E2%80%93query_separation

No, sorry, I just mentioned that an assembly containing IL code is easier to decompile than an ACCDE file. That's just the technical point of view. You've mixed this up with the context in which it is used. 'Normally', the end user does not have administrative access to a SQL Server or its...

Unfortunately, I don't quite follow. The only thing I understand is that you are saying that Access (VBA), is not capable of performing your calculations. If that is the case, then there is no need to talk about VBA as the host for your calculation function (anymore), right? And that also rules...

Just a note: A .NET assembly containing IL code generally offers less protection against decompilation than an ACCDE (see, for example, the ILSpy tool). If you want to go down this route, you should at least consider obfuscation (e.g. using ConfuserEx). A native assembly would be more secure...

Thank you @MarkK . I already use this. I'm more or less a keyboard junkie. ;)

Sure. But it wouldn't behave like a renamed accdE.