Prev: Why Do 2 Rows Disappear from my DataGridView?
Next: RollUp by Date
From: Rick Rothstein on 24 Apr 2010 18:44
I assumed the OP was saying "script" in the general sense meaning program
code and not specifically meaning VBScript code. Over in the Excel groups
where I hang out now, many of those posting questions say VB script when
they mean VBA code.

--
Rick (MVP - Excel)



"Mayayana" <mayayana(a)invalid.nospam> wrote in message
news:ea29s#64KHA.1888(a)TK2MSFTNGP05.phx.gbl...
>
>
> | > Set SH = CreateObject("WScript.Shell")
> | > SH.Run "notepad.exe"
> |
> | Or maybe even this one-liner...
> |
> | Shell "notepad.exe"
> |
>
> There's no Shell method in VBS. The
> following works, but it's confusing, hard to
> debug, and blurs the object instantiation --
> making it pretty much indecipherable to
> new people:
>
> CreateObject("WScript.Shell").Run "notepad.exe"
>
>
From: Mayayana on 24 Apr 2010 23:41
|I assumed the OP was saying "script" in the general sense meaning program
| code and not specifically meaning VBScript code. Over in the Excel groups
| where I hang out now, many of those posting questions say VB script when
| they mean VBA code.
|

I suppose I should have added VBA to the explanation
of what's not VBS. I always forget about VBA because I've
never used MS Office, and VBA is really a custom tool
specific to particular software.

But you might have guessed right. I'm forever surprised
by how provincial MS Office users are. Most assume that
the whole world uses MS Office. And they act accordingly,
doing things like sending an 80 KB doc or docx in email with
a note: "Here's that phone number you wanted." (On the
other hand, I don't think I've ever met an MS Office user
who knows about Notepad. :)

People often talk about Word, etc. in the VBS group, but
in that case they really are talking about script -- automating
the Office objects.


From: GS on 25 Apr 2010 12:04
Adding to your comments...

Mayayana used his keyboard to write :
>> I assumed the OP was saying "script" in the general sense meaning program
>> code and not specifically meaning VBScript code. Over in the Excel groups
>> where I hang out now, many of those posting questions say VB script when
>> they mean VBA code.
>>
>
> I suppose I should have added VBA to the explanation
> of what's not VBS. I always forget about VBA because I've
> never used MS Office, and VBA is really a custom tool
> specific to particular software.
>
> But you might have guessed right. I'm forever surprised
> by how provincial MS Office users are. Most assume that
> the whole world uses MS Office. And they act accordingly,
> doing things like sending an 80 KB doc or docx in email with

How right you are! Adding to that is MSO12+ users also assume the rest
of the world uses that version. Granting that MS provides utilities for
earlier versions to open/read the later version files, it's no excuse
to not be aware of v12+ MSO apps to generate earlier version files.

> a note: "Here's that phone number you wanted." (On the
> other hand, I don't think I've ever met an MS Office user
> who knows about Notepad. :)
>
> People often talk about Word, etc. in the VBS group, but
> in that case they really are talking about script -- automating
> the Office objects.

What amazes me is that they don't know that most all M$O apps now
support VBA for automating. The only reason I can think of to use some
other language to automate M$O apps is for code security. Otherwise,
the ability to automate is built in!

Also, VBA isn't limited to just M$O apps; ..more and more software now
supports built in automation by licensing VBA from M$. <BTW> I see M$
has released VBA7 for the 64-bit versions of M$O. Where's VB7 for
64-bit Windows????


From: Mike B on 25 Apr 2010 12:51

"GS" <GS(a)discussions.microsoft.com> wrote in message
news:e3pP4DJ5KHA.5880(a)TK2MSFTNGP04.phx.gbl...
> Adding to your comments...
>
<snip>

> Also, VBA isn't limited to just M$O apps; ..more and more software now
> supports built in automation by licensing VBA from M$. <BTW> I see M$ has
> released VBA7 for the 64-bit versions of M$O. Where's VB7 for 64-bit
> Windows????

<groan> and off we go.....
>
>



From: Nobody on 25 Apr 2010 13:16
"GS" <GS(a)discussions.microsoft.com> wrote in message
news:e3pP4DJ5KHA.5880(a)TK2MSFTNGP04.phx.gbl...
> Also, VBA isn't limited to just M$O apps; ..more and more software now
> supports built in automation by licensing VBA from M$. <BTW> I see M$ has
> released VBA7 for the 64-bit versions of M$O. Where's VB7 for 64-bit
> Windows????

Off topic: MS stopped licensing VBA for new customers. It's basically in
maintenance mode. New customers who want VBA have to use the .Nxt variant.

http://msdn.microsoft.com/en-us/vstudio/aa700828.aspx


First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4 5
Prev: Why Do 2 Rows Disappear from my DataGridView?
Next: RollUp by Date