some problems in writing script

[H_SH]

Hello Everyone,

I am using DIAdem 10.2

1) I am writing Script for my scada system's reporting. In my reporting template there are some common text field like User, Designation, reoprt period, report number etc etc... i designed the dialog box to ask these details in starting and now i wanted to transfer these details on every page of report.. Is there any way to connect these details with reporting template?

2) I am facing problem in path allocation inside script.. Is there any way to get rid off from problems arising due to file movement of *.sud file or *.tdr file. It will be great if diadem automatiocally search inside the folder where script is saved.. so whenever we will move complete folder of any reporting. It will not create any problem provided we save all file inside one folder.

3) I wanted to run my script over different system or sometime need to distribute it. Is there any way to make My script run over other system where DIAdem is not installed.. any way of it, even making it available using any programming platform like LabVIEW, Measurement studio , CVI etc etc

Thanks Alot !

HS

[Twigeater · Accepted solution]

Hello HS!

1) You can use global variables to resolve that task. There are some predefined like 'T1' or - what I prefer -  allocate them in Script via the GlobalDim command and fill them with your data. In the report you can use the expression '@@T1@@' or '@@MyGlobalDimVar@@' in text fields to display the content.

2) You can use the AutoActPath variable to make all file access relative to the running script. If you pack all your files beside the script you can move the package where ever you want in the file system. In all Load commands like PicFileLoad you have to use AutoActPath.

3) You can run DIAdem Scripts and Dialogs only in DIAdem.

Matthias

[H_SH]

Hello Matthias,

Thanks for Reply and solution..

1) Solved and worked well

2) Solved and worked well

3) This is problem    how come a system integrator force the client to purchase DIAdem for every system where he wants to run or have reporting. and if clients become ready then also Integrator will have less margin in developing the reporting template for them which is platform dependent . DIAdem is very gud and efficient in making quick reports.. Why not NI is thinking to add the feature of distribution kit?

Any way thats the question to NI ..

Thanks Again for your help

HS

[Brad_Turpin]

Hi HS,

1)  Depending on the situation, Root, Group, or Channel properties are also an excellent location to store scalar data that you want to dynamically show on a REPORT layout.  Also, if you want the same information to appear in all REPORT sheets, you should consider using REPORT Master Layouts (available in DIAdem 10.2 and later).

2)  I ALWAYS use AutoActPath exactly as Matthias suggested.

3)  DIAdem is always required to run a VBScript that makes function calls (the "red" ones in the SCRIPT editor) that are only available in DIAdem.  You can serve up a DIAdem application over the network using commercially available terminal services such as Citrix, or you can use DIAdem concurrent licensing to share N licenses among 10N or 100N (etc.) users.  Note also that the DIAdem Base (least expensive) version will run ALL VBScripts you have created in DIAdem Advanced or DIAdem Professional.

Brad Turpin
DIAdem Product Support Engineer
National Instruments