Re: Why no delayed trigger on newer DSOs?
- From: "Joel Kolstad" <JKolstad71HatesSpam@xxxxxxxxx>
- Date: Wed, 15 Aug 2007 09:27:54 -0700
"Joerg" <notthisjoergsch@xxxxxxxxxxxxxxxxxxxxx> wrote in message
news:NiFwi.1129$i75.49@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
However, I am not an expert (yet) in VBA so I can't do any processing
on-the-fly. But I'll learn it. Was hoping it was C and not Basic but, oh
well, I guess that was Bill Gates' decision.
If you really want to get ambitious, note that VBA (as provided in
Word/Excel/etc.) will let you access COM objects which -- for the purpose of
this discussion -- boils down to nothing more than a function call interface
with a prescribed set of data types and calling conventions. COM objects can
be programmed (implemented) using C++ (and plenty of them are), although it's
much easier to write them using one of the ".Net" languages such as C#.
Realistically I think Gates' choice of VBA rather than C for Office makes
sense... I know office workers who have absolutely zero formal programming
background, and they can manage to modify and write various little utilities
and macros in VBA, whereas I think they'd find the initial learning curve a
lot steeper with C and wouldn't even bother with it.
---Joel
.
- Follow-Ups:
- Re: Why no delayed trigger on newer DSOs?
- From: Joerg
- Re: Why no delayed trigger on newer DSOs?
- References:
- Why no delayed trigger on newer DSOs?
- From: Joerg
- Re: Why no delayed trigger on newer DSOs?
- From: Rich Grise
- Re: Why no delayed trigger on newer DSOs?
- From: Joerg
- Re: Why no delayed trigger on newer DSOs?
- From: Fred Bartoli
- Re: Why no delayed trigger on newer DSOs?
- From: Joerg
- Why no delayed trigger on newer DSOs?
- Prev by Date: Re: Utah Mine Disaster and Robots
- Next by Date: Re: Utah Mine Disaster and Robots
- Previous by thread: Re: Why no delayed trigger on newer DSOs?
- Next by thread: Re: Why no delayed trigger on newer DSOs?
- Index(es):
Relevant Pages
|