The treatment of user parameters is different in WINDOX 5, compared to WINDOX 4.
Not only the parameter values (displayed in the white fields of the parameters page) but also the designations (the labels) and types (number, string, date) of the 10 user parameters are stored individually for every measurement.
So, if the user changes the name or value of a parameter and clicks "save", the effect is on that single measurement only.
This new behaviour of the software with regard to parameters is necessary in a multi-user environment which is much better supported by WINDOX 5 as by WINDOX 4.
Example:
If user A on his PC sets the name of Parameter 1 to "operator" (type "string"), while user B on his PC, connected to the same database server and same database, sets the name of Parameter 1 to "environmental temperature" (type "number"). Both perform measurements with their settings. This must not interfere, because both users do not (and can not) know that there is another user with different preferences.
Of course, this implies a disadvantage for single users who simply forgot to set their parameter names properly prior to the measurement(s). There is no way to change the properties by a general set-up, as with WINDOX 4.
But there is a way in WINDOX 5, too, it is only a bit more work. There is a new Application program statement, DEFUSERPARx (x=1 to 10) to set the properties of the parameters, as used in the sample program listing below:
MAIN
FIRSTPKEY // recalls first measurement in database, (mind browser filter!)
REPEAT
S1=REPORT,"@PAR(1)" // memorize first parameter value
S2=REPORT,"@PAR(2)" // memorize second parameter value
DEFUSERPAR1 0,"USER","",0
DEFUSERPAR2 0,"LOT","",0
P1=S1 // restore value of parameter 1
P2=S2 // restore value of parameter 2
STOREMINFO // store in database
NEXTPKEY // proceed to next measurement (mind browser filter!)
UNTIL ERRORNUMBER<>0 // until there is no next measurement
END