Re: The problem with not owning the software

On Tue, 31 Dec 2024 19:32:19 -0500, DFS wrote:

On 12/31/2024 2:25 PM, rbowman wrote:

On Tue, 31 Dec 2024 02:18:09 -0500, DFS wrote:
 

On 12/30/2024 7:59 PM, Lawrence D'Oliveiro wrote:

On Mon, 30 Dec 2024 18:58:06 -0500, DFS wrote:
>

If you ever do need to automate office software or build custom
applications, you'll find that MS Office and VBA is extremely
superior to ALL other office software.

>
Unfortunately, no.

>
You have NO idea what you're talking about.
>
>
  > Even Microsoft realizes that VBA is crap, which is why it is
  > offering Python access to Excel users -- at a cost, of course.
>
Python can't come close to replacing VBA (and vice versa of course).

 
Esri did a good job of replacing VBA.
 
https://www.esri.com/arcgis-blog/products/arcgis-desktop/3d-gis/arcgis-
desktop-and-vba-moving-forward/?

rmedium=redirect&rsource=blogs.esri.com/

esri/arcgis/2016/11/14/arcgis-desktop-and-vba-moving-forward
 
They had their own scripting language, Avenue, and switched to VBA over
20 years ago,
 
https://www.esri.com/news/arcnews/fall02articles/new-tool.html

 
 
The best embedded scripting language I came across was Borland ObjectPAL
(a derivative of Delphi), included with Borland Paradox for Windows in
the early-mid 90s.  PDoxWin lives on in WordPerfect Office; not sure if
it still uses ObjectPAL.  WP includes a limited VBA.

My first experience with Windows was using the Borland IDE and OWL. I
liked it better than MFC but when you're the 700 pound gorilla...

For a whil MS would dearly e VBA and Python coexisted, but VBA was

phased out.

 
Of what?

Esri. Try to follow along.

Enjoy living in the past.

 
VBA is thriving in Office 2024 and 365.  Get with the present.

As I've mentioned many times I have never used Office so I haven't
followed VBA. I have a suspicion that like WinForms MS would dearly love
to drown VBA in a bathtub but there is too much baggage. I'm not sure
they've even managed to eradicate classic Visual Basic. There was a whole
cottage industry of VB controls that didn't transfer to VB .NET afaik.