VBScript Reference Manual for InduSoft Web Studio

More documents

Recommendations

Info

VBScript Reference Manual InduSoft Web Studio IWS implements Visual Basic Script Edition 5.5 or higher, and functions as the “host” for VBScript. IWS provides an integrated development environment where the HMI/SCADA application developer can take advantage of the functionality and ease of use of VBScript, yet have access to all IWS tags and all built-in functions directly from VBScript. The diagram below illustrates the IWS architecture. Since VBScript is an interpreted language, the VBScript Engine parses the language at runtime and executes commands subject to limitations placed by the VBScript Host. InduSoft allows VBScript code to be located several areas in an IWS application: • Global Procedures. This is an area for subroutines and functions that can be called by any other VBScript routine, or by a built-in IWS function (requires IWS Version 6.1 Service Pack 1 or later). • Graphic Script. Code in this area gets executed whenever any graphics (screens) are active. • Screen Script. This is where code is executed when an individual screen is active. • Command Dynamic. When an object has a Command Dynamic, one option is to run VBScript code. • ActiveX Events. A VBScript code segment can be run based on an ActiveX event • Background Task. VBScript code can be running as a background task. One or more VBScript groups are supported, allowing conditional processing of the various VBScript background tasks. This subject is covered more completely later in the VBScript Configuration and Operation in IWS section. InduSoft Web Studio Version 6.1 Internal Architecture 6 InduSoft, Ltd.
InduSoft Web Studio VBScript Reference Manual In a Web Thin Client configuration, VBScripts associated with a screen can run either on the workstation runtime display or on a Web Thin Client station running Microsoft Internet Explorer. The VBScript routines that can execute on a Web Thin Client include those located in a Screen Script, a Command Dynamic, and an ActiveX Event. Since VBScript runs on all Microsoft operating system platforms, there are no limitations to VBScript running on any Microsoft compatible platform. VBScript Limitations in IWS Microsoft initially developed VBScript to work with websites (web pages). In the web server environment, VBScript was designed to work with the Windows Scripting host and ASP, which provide file access and form generation. On the web client side, VBScript was designed to work with Microsoft Internet Explorer using HTML and DHTML, which provide display generation. So as a result of the initial design goals, VBScript does not have much in the way of built-in language support for Forms, File I/O, Communications or direct Printing control. Additionally, IWS has its own built-in web server and does not use ASP. By using IWS built-in functions, ActiveX controls and Microsoft Office Applications (or components), there are several methods for workarounds to these limitations as well as to extend VBScript’s capability. The following are some of VBScript’s limitations and workarounds. Item VBScript Workarounds Forms Does not support Use IWS objects for user interface, pass parameters to IWS. Can also use ActiveX Controls. File I/O Limited support directly Use Scripting Objects and/or IWS built-in functions. Can also use ActiveX Controls. Communications Does not directly support Use IWS built-in functions or 3 rd party ActiveX controls Printing Does not directly support Use Microsoft Office Applications or IWS built-in functions Charting/Graphing Does not directly support Use IWS trending, Microsoft Office Applications, Microsoft Office Components, or 3 rd party ActiveX controls DDE Does not support Supported in IWS built-in commands (not under Windows CE). InduSoft, Ltd. 7
Page 1 and 2: VBScript Reference Manual for InduS
Page 3 and 4: InduSoft Web Studio VBScript Refere
Page 5: InduSoft Web Studio VBScript Refere
Page 41: InduSoft Web Studio VBScript Refere
Page 44 and 45: VBScript Reference Manual InduSoft
Page 56 and 57:
VBScript Reference Manual InduSoft
Page 58 and 59:
Page 60 and 61:
Page 62 and 63:
Page 64 and 65:
Page 66 and 67:
Page 68 and 69:
Page 70 and 71:
Page 72 and 73:
Page 74 and 75:
Page 76 and 77:
Page 78 and 79:
Page 80 and 81:
Page 82 and 83:
Page 84 and 85:
Page 86 and 87:
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
Page 100 and 101:
Page 102 and 103:
Page 104 and 105:
Page 106 and 107:
Page 108 and 109:
Page 110 and 111:
Page 112 and 113:
Page 114 and 115:
Page 116 and 117:
Page 118 and 119:
Page 120:
Page 123 and 124:
InduSoft Web Studio VBScript Refere
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Page 255:
show all

VBScript Reference Manual for InduSoft Web Studio

Create successful ePaper yourself

Delete template?

Save as template?