Do not post any licensing information in this forum.
The Office VBA editor is more approproaite.
PrimalScript is Excelent at building VBScript scripts that access Office products.
Here ios an example of using VBScript to adcess Excel:
sExcelFile = "f:testdest.xlsx"
Set xl = CreateObject("Excel.Application")
Set xlBk = xl.Workbooks.Open(sExcelFile)
An example of listing riules from Outlook:
Set outlook = CreateObject("Outlook.Application")
Set colRules = outlook.Session.defaultstore.getrules()
For Each rule In colRules
For Each Action In rule.Actions
If Action.ActionType = 1 And Action.Enabled Then
WScript.Echo "Move To Folder: " & Action.Folder.Name
We can run against MSAccess the same way. All of this can be built and debugged in PrimalScript. We cannot build design or debug forms, reports, HTML pages or any of the MSAccess objects. We can build and query tables from VBScript. We can use PS to type and manage VBA functiiona na Subs but not when in a project file.
VBA is not a scripting langauge it is a subset of VB and is a fully compiled langauge (VB compiled). VBA cannot even be managed in Visual Studio. Each instance of a VBA project is intimately tied to the Office product that it lives in.
Who is online
Users browsing this forum: No registered users and 3 guests