Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.basic.visual.misc > #2351
| From | GS <gs@v.invalid> |
|---|---|
| Newsgroups | comp.lang.basic.visual.misc, microsoft.public.vb.general.discussion |
| Subject | Re: ShellExecute broken in Win10 |
| Date | 2017-05-09 14:41 -0400 |
| Organization | A noiseless patient Spider |
| Message-ID | <oet2b2$j41$1@dont-email.me> (permalink) |
| References | <oeqta7$aqi$1@dont-email.me> <oerad0$4n3$1@dont-email.me> <oeranb$5f0$1@dont-email.me> <20170509095822.00001d8c@eternal-september.org> |
Cross-posted to 2 groups.
> or > > * there's a bug in your VBA code As stated.., my VB6 version uses the same exact code; -it works as expected. I'm now assuming this is a VBA issue and nothing to do with VB6 since it seems to be working there just as it does for Gry Scott. My fault for not checking this out! I normally dev new stuff in VBA 1st to work out the logistics, then make a VB6 version using the same code. When I discovered the lcase issue I googled it and got lots of reading that confirmed it to be a Win10 ShellExecute issue. > > :) that said, check these out > > http://stackoverflow.com/questions/29847933/vb-6-0-open-default-email-client-and-populate-some-entries > > http://stackoverflow.com/questions/25906657/encodeuricomponent-or-escape-in-vb6 > Neither of these offer anything helpful. Thanks, though, for making the effort... > also, and since we're at it; here's an alternate idea, instead of > shelling out the string, you may let the system do it for you, the idea > is the following: > > Add a form to your app > > Add a "web browser" control to the form and a button to close it > > Populate the webbrowser HTML with some text and a "mailto" URL and > ensure to properly "HTMLencode" the URL > > now, when clicking the URL, the mail client will open and populate with > the given fields (mailto, body...) The procedure is already fired by a form button so I might be willing to explore this at some time in the future if I really need to have the user intervene in the product registration process. Since that's not necessary I decided to go with CDO for this task. I've also revised my registration manager to do same for sending activation keys to users. Since the issue lies with a VBA problem, I can use Excel's built-in 'Send to > Mail Recipient' functionality for all other stuff that doesn't require being in Base64 format. -- Garry Free usenet access at http://www.eternal-september.org Classic VB Users Regroup! comp.lang.basic.visual.misc microsoft.public.vb.general.discussion
Back to comp.lang.basic.visual.misc | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
ShellExecute broken in Win10 GS <gs@v.invalid> - 2017-05-08 19:03 -0400
Re: ShellExecute broken in Win10 Gary Scott <garylscott@sbcglobal.net> - 2017-05-08 19:16 -0500
Re: ShellExecute broken in Win10 GS <gs@v.invalid> - 2017-05-08 22:11 -0400
Re: ShellExecute broken in Win10 Gary Scott <garylscott@sbcglobal.net> - 2017-05-09 08:12 -0500
Re: ShellExecute broken in Win10 GS <gs@v.invalid> - 2017-05-09 11:58 -0400
Re: ShellExecute broken in Win10 Gary Scott <garylscott@sbcglobal.net> - 2017-05-09 20:26 -0500
Re: ShellExecute broken in Win10 GS <gs@v.invalid> - 2017-05-10 01:01 -0400
Re: ShellExecute broken in Win10 GS <gs@v.invalid> - 2017-05-08 22:46 -0400
Re: ShellExecute broken in Win10 GS <gs@v.invalid> - 2017-05-08 22:52 -0400
Re: ShellExecute broken in Win10 Arne Saknussemm <esre.10.arnsak@spamgourmet.com> - 2017-05-09 09:58 +0200
Re: ShellExecute broken in Win10 GS <gs@v.invalid> - 2017-05-09 14:13 -0400
Re: ShellExecute broken in Win10 GS <gs@v.invalid> - 2017-05-09 14:41 -0400
Re: ShellExecute broken in Win10 - Mystery solved! GS <gs@v.invalid> - 2017-05-10 12:50 -0400
csiph-web