-
Status Field Not Properly Displayed
The information in this article applies to product: e-Work 6.5 Issue * Status fields display the wrong status, and/or "Unknown field 'Status1' in " is written to the Windows event log, where 'Status1' is the name of the Status field. Resolution * Run the e-Work stored procedures against the database. For SQL Server, run…
-
Form Names with Illegal Characters
The information in this article applies to product: e-Work 6.x Issue * Under certain circumstances, it is possible to create form names that contain illegal characters. Resolution * Although it should not be possible, illegal characters (see the Designer User Manual for the complete list) can be inserted into form names…
-
Improved Performance When Using %ScriptAsync
The information in this article applies to product: e-Work 6.0 - 6.5 Discussion * The performance of calls to the %ScriptAsync function can be improved by omitting the map name and procedure name arguments and using a filename argument instead. For example, %ScriptAsync(JScript,"", %Procedure.Name, %MapName, "SendMail()");…
-
Integration Wizard May Create Wrong Number of Parameters for %ExecProc
The information in this article applies to product: e-Work 6.5 6.6 Issue * When using the Integration Wizard to generate the syntax for the function %ExecProc, 3 parameters are created regardless of the number specified in the wizard. If the stored procedure does not take 3 arguments, an error is generated when it is…
-
Map and Administrative Form Group Duplicate Names
The information in this article applies to product: e-Work 6.x Issue * Under certain circumstances, it is possible to create multiple maps and administrative form groups with the same name. This will cause procedures to function incorrectly. Resolution * When an attempt is made in the Procedure Explorer to rename a map or…