Windows API in VBA - Strings (Part 1)

[@ericturner5154]

It's about time somebody decided to do a thoughtful consideration of the subject matter. Your videos compliment nicely information that's already available and fill in some very important holes. Hopefully we're going to get into even more in-depth topics like MDI windows, Device Context and the like... We'll Done!

[@codekabinettcomen]

I'lll see what I can do.

[@ziweitan]

Definitely and this tutorial is the best out there for beginners to learn and understand what windows api actually is.

[@xavierbatlle1828]

Thanks! It's surprising and very interesting. 😮. Going to part2 inmediately.

[@bradmccoy1747]

Im liking this shtuff! I do have an opinion as to why the vba string needs to pass as ByVal. 3-2-1 Go: So the function will only accept it one way; and it wants a memory address to a string given to it. Changing the declaration will only change how it sends. I think VBA would let you put the ByVal directly into the parameter listing of the function call. Because changing the declaration may confuse things. But the BSTR variable in VBA has an address but that is not what the api function wants. The BSTR variable also has a value and that is the address to the actual string; and that is what the api function wants.

[@bluxer4225]

Great and rare stuff here.

[@zoltangyulatoth894]

Thank you for sharing !

[@johnclark851]

"You're still here?!?" Thanks for the laugh this morning!

[@GroverParkGeorge]

Brilliant.

[@sanjaykarmkar9853]

Sir First I like to thank you for your effort for providing such valuable content. I want to access com port through VBA in MS Access for data collection and manipulation, please guide

[@codekabinettcomen]

Sorry, my experience with accessing the COM port with VBA was ages ago. I used an ActiveX component back then. - That's all I can say about that for now.

[@عليعلي-ن1خ3ص]

Nice explanation as usual: Question:- Regarding the need to use string buffers for memory management as you nicely explained towards the end of the video, wouldn't it be possible for the api function to simply return the string then our vba code would just store it in a variable for later use? That way, the windows api could release the allocated memory immediatly after its return but the vba code would still have a copy of the string and be resposible for releasing the associated memory when done with it.

[@twiddle7125]

Is it possible to use the Win32 API to allow a VBA custom class which extends the Array type to iterate with a For Each loop using its default member? I have found only a couple of results online, but they either don't work or don't work for 64 bit.

[@codekabinettcomen]

Interesting. I don't quite understand what You mean. Can you provide a more extensive description of what you are trying to do?

[@SAMYTAHER]

√√√