VBScript is being deprecated in future releases of Windows

Brink said:

Source:

Deprecated features in the Windows client

Review the list of features that Microsoft is no longer actively developing in Windows 10 and Windows 11.

learn.microsoft.com

Resources for deprecated features in the Windows client

Resources and details for deprecated features in the Windows client.

learn.microsoft.com

See also:

Install or Uninstall VBScript Feature in Windows 11

This tutorial will show you how to install or uninstall the VBScript optional feature for all users in Windows 11. A .vbs file is a Virtual Basic script written in the VBScript scripting language. It contains code that can be executed within Windows via the Windows-based script host...

www.elevenforum.com

Click to expand...

Hi @Brink

What then happens to all those EXCEL macros written in VBS. Ms must provide similar or loads of queries and procedures will just stop working. That will please a load I'm sure. !!! In Woed and Power point not so much of an issue.

If One can't query SQL databases to bring data into EXCEL and run procedures it's going to limit the usefullnes of EXCEL quite a lot.

Cheers
jimbo

What about the VB-like programming language that is built in to all Office apps?

In particular, there are many small businesses that depend on Access database apps written in VB.

Birk said:

What about the VB-like programming language that is built in to all Office apps?

In particular, there are many small businesses that depend on Access database apps written in VB.

Click to expand...

Word and EXCEL I know use vbs -- I have loads of spreadsheets with lots of macros in them as I'm sure so do many others. I'm sure businesses don't want to waste a load of time and expense by re-writing these EXCEL sheets -- also some are archived for years.

I wonder if Ms has really thought this one out -- I sort of doubt it.- I often retrieve data from SQL databases such as Mariadb and extract to worksheets in EXCEL

e.g








cheers
jimbo

I don't understand why people are reading
VBScript, [Visual Basic Script, VBS]
but thinking
Visual Basic for Applications [VBA]
which is what MSOffice components such as Excel & Access use for scripting.
MS's announcement only mentions VBScript [VBS]

VBA only uses VBS methods when expressly & specifically loaded as a Reference [Microsoft scripting runtime].
If I remember correctly, I need that Reference if my VBA uses the FileSystemObject which is, strictly speaking, not part of VBS but its methods just make it look like it is.



All the best,
Denis

It is about time they got rid of it, I disable it since XP and I never missed it. It is only abused by malware.
Now lets do the same with PowerShell 5 and Windows will be finally safe by default, well except for lolbins.

Try3 said:

I don't understand why people are reading
VBScript, [Visual Basic Script, VBS]
but thinking
Visual Basic for Applications [VBA]
which is what MSOffice components such as Excel & Access use for scripting.
MS's announcement only mentions VBScript [VBS]

VBA only uses VBS methods when expressly & specifically loaded as a Reference [Microsoft scripting runtime].
If I remember correctly, I need that Reference if my VBA uses the FileSystemObject which is, strictly speaking, not part of VBS but its methods just make it look like it is.
View attachment 74192


All the best,
Denis

Click to expand...

How do you separate VBS from VBA -- it's at executable level I.E it will be at the .exe level where problems will arise.

E.g I could have a thing called Rottweiler.bite -- which is say a wrap around of Rottweiler.exe. (Sorry for my doggy things today - but I wasn't going SHOPPING on a Sat afternoon whatever SHE said, and I love my dogs).

You could deprecate things running on Rottweiler.bite but the internal apps needing Rottweiler.exe would still need that executable.

This will be the problem with deprecating vbs even if vba will still run. And if vbs is deprecated how will you call vba to run it,

Cheers

jimbo

We seem to be talking at cross-purposes.

VBA continues to work even if VBS is disabled.

VBS has been disabled on this computer

yet

---

jimbo45 said:

How do you separate VBS from VBA

Click to expand...

They exist separately.

jimbo45 said:

it's at executable level I.E it will be at the .exe level where problems will arise

Click to expand...

VBA does not create .exe files. It exists as code in the Visual Basic Editor of MSOffice applications.

jimbo45 said:

E.g I could have a thing called Rottweiler.bite -- which is say a wrap around of Rottweiler.exe

Click to expand...

Since we are discussing VBA then what you would have would be a spreadsheet called Rottweiler.xlsm [or Rottweiler.xlam if it's structured as an add-in for use within one or more spreadsheets].

jimbo45 said:

if vbs is deprecated how will you call vba to run it

Click to expand...

The same way I do now. I open an MSOffice file and I run the VBA code that is within the Visual Basic Editor of that file.




Merry Christmas,
Denis

Try3 said:

We seem to be talking at cross-purposes.

VBA continues to work even if VBS is disabled.

VBS has been disabled on this computer
View attachment 74217
yet

View attachment 74218

---

They exist separately.


VBA does not create .exe files. It exists as code in the Visual Basic Editor of MSOffice applications.


Since we are discussing VBA then what you would have would be a spreadsheet called Rottweiler.xlsm [or Rottweiler.xlam if it's structured as an add-in for use within one or more spreadsheets].


The same way I do now. I open an MSOffice file and I run the VBA code that is within the Visual Basic Editor of that file.




Merry Christmas,
Denis

Click to expand...

Thanks for clearing that up == wasn't clear from the Ms directive,

Cheers
jimbo