Confuzzled

What is the return code for the non-working InetGetSize call? Have you considered testing for a non-zero one each and every time you call it?

Mixing AutoIT and VBA scripts and macros, in a ten year old thread. Whatever could go wrong? OutlookEX UDF is one way of doing it, and VBA is a completely different way of doing it.

I'm going to sincerely thank you for your effort to post added 22 lines of code to bypass an easily fixable issue. The entire AutoIT cohort is welcome to add the code as a wrapper to 'fix' the issue. See any issues with that statement? Looks like Neil and Jos are already on the correct solution. I await the new version with the simple fix rolled out.

I was running it on a Windows 10 machine, not a quantum computer! You have just proved my point - nobody knows the units, as they are not mentioned, and not in a understandable format.

He asked to report it to the mailing list as a feature request, or write a wrapper around it (as Musashi suggested) Sorry to have wasted everybody's time (pun intended) - I will just write shorter code in the future.

It wasn't even four hours - just "1.306e+004" and I think it is seconds, based on the second part of my first post. The point is it should be shown, and be understandable. Scientific notation is for scientists, not coders!

Is your exe signed and registered in the Microsoft Store? Nope? Then it probably will throw an exception and need a manual override to be saved. FileInstall was a good idea and I have used it for many things, but it wont be very useful for exe droppers much more, as AutoIT compiled exe files are recognised (misclassified but that is irrelevant for most users that are running your wrapper code) as badware. The skript kiddies with their silly malware have spoiled it for everybody.

Given you are adding to a closed source product you have no control over, and are accessing over published APIs, any subsequent changes to the underlying structure of any metadata stored by Microsoft would be deal breaker for your software should users update their Microsoft software, a uncontrollable event you cannot allow for. Keep your data separate is my strong advice. Is it possible for you to run two copies of Microsoft Office side by side on a widescreen monitor to obtain some of the functionality you are seeking? Of course they cannot be synced programmatically, but at least you could have a different viewport on one to the other (I suspect). The other option is to join the Microsoft beta program and make suggestions to the coding team. Should the need be identified that would bring in massive profit boosts, I suspect it would be added quickly enough. Are you sure that the product you are using is suitable for what your needs are? Are you putting lipstick on a pig? Example: Financial accountants using Excel for database functionality.

To identify candidates for the Darwin Awards!

It bugged you since December 14th, 2018? Ouch! Is the problem with the contents of the variable as it arrives to AutoIT from VS or SSMS, as it is stored on the clipboard by Windoze, or when it is pasted to OneNote? Has the advent of Windows 10 and clipboard changes upset the underlying code presumptions? PS: Do you close and destroy your Word object?

A very big ask for a first project! It *CAN* be done as water has pointed out. A heads up: Do not mix your objects, arrays, and strings. Know when you are accessing pointers to an object, and when you are accessing the contents. Most arrays are zero based. Often the zero index contains a count. This can trip you up in loops, with subscript out of range errors. Use _ArrayDisplay liberally for debugging. Comment it out as you get that part of your code under control. You can always uncomment it later if a later step proves troublesome. Name your variables to be self descriptive. $string1 as a global variable is not going to help two thousand lines down. Use lots of comments in your code. Drop hints to yourself for what you are trying to do. ConsoleWrite is your friend for debugging. Even if you don't incorporate error processing into your project from the word go (dangerous), at least write out the return codes for each step to the console, along with where you are up to, and the value of the variable you are processing. For processing efficiency, when doing a search for items in the $Outlook object, make it as narrow as possible as soon as possible. As you have done, the best way to get help here is to show what you have done, and where you are stumbling. Everybody will jump in with hints and solutions.

GitHub is now owned by Microsoft, isn't it? Are they giving you a job offer? No strings attached open source development co-sponsorship? Sounds wonderful.

Looks like internal @LogonDomain and@LogonServer system macros don't do the job for you. You need @LogonWorkGroup too? Wonder if the functionality behind the extraction of those system macros is faulty, or looking at different things?

PS: I went back in to the help file and there is one example in (wait for it), Frequently Asked Questions (FAQ), Item 6 to be specific. Matthew 7:7-8, King James Version

Funny that, I was just looking up the documentation for the SEND function the other day in the AutoIt help file, and was wondering about the option flag (default/raw), and noticed the examples didn't show much for the second option. The SendKeyList wasn't of much use either. I experimented, had to split my strings into some of one and some of the other, all ending up concatenated, and it turned out OK, but not really sure why. I'll go back and read a bit further later, but in the meantime my code is working. Good luck with the documentation. A little bit of flushing out of examples may be in order.