This question is similar to the one posed in the follwing post:
http://community.emerson.com/process/emerson-exchange/systems-solutions/deltav/f/50/t/2282.aspx
On calling frszOpenTagForm Me to open the search utility within DeltaV Operate, I get a Workspace Application Error Number 5(5) "Invalid procedure call or argument". MSDN insinuates something may be out of range (http://msdn.microsoft.com/en-us/library/aa445484(v=vs.60).aspx) in the procedure.
The error pops up every time the search window appears and once I click OK, the search window closes and reopens. This happens on all workstations, but I don't see any other adverse effects or missing data. Any ideas on what may be causing this? No changes have been made to the VB code. I have searched for invalid characters in the DESC fields in MODT.SCR and fixed all 4.
Thanks.
James Suisse
Did you fix the invaild characters by modifying the modt.scr file or some other method?
In reply to Tyler Anderson:
The likely reason there are invalid characters in the modt.scr file is that those characters exist in the
description, main display, faceplate, or detail display field of the module in the control database. This can happen when bulk importing modules (line feed/carriage returns/tabs) or if an apostrophe is in any one of those fields.
For example, one line from the file looks like this:
MODTI { NAME='module' DEVID=############# AREA=# CDISP='display' IDISP='faceplate' DDISP='detail' DESC='description' }
If description has an apostrophe, the parser sees an uneven amount of apostrophes and fails.
Essentially, the fix is to bulk export the problematic fields for ALL modules, fix the fields in the export file, then bulk import the corrected configuration.
In reply to Youssef.El-Bahtimy:
I had the same problem in my database after a bulk import. My problem didn't end with the modt.scr. After downloading setup data to clear up the modt.scr, the issue continued until to create more problems in my database and in the operator graphics. I would suggest that you call tech support and let them help you through the process to get things back on track. It is not simply changing the modt.scr. Also, I was told by tech support that the bulk export/import file should not have a description as the last field in the bulk file. It is this description as the last field in the bulk import file that caused my problem. While other characters in descriptions can cause a problem, this was not what caused our issues. Please call tech support if you have not cleared up your problem, and make sure that bulk import/export files do not have descriptions as the last field.
In reply to Deb Colclazier:
To add a couple things...
1) You'll have to change the module properties and download. Do not modify the modt.scr file yourself. (Open the module properties, clear out the description, hit ok. Re-open the module properties and add the description back, hit ok. Download when safe.)
2) Be careful with bulk edit. (With great power, comes great responsibilty...) Bulk Edit offers 1001 ways to mess up your database. (It can also save a ton of time...) A couple tips:
Good luck! And if you have any questions, don't hesitate to call the GSC! They are there to help!
Actually, the bulk edit data file does not support any "String" type parameter to be the last parameter in the format columns. This is because after this, there is "carriage return" considered to go to next line, which is considered as part of string itself. But this presents as an import error during the user defined import itself. Secondly, if this is the case, this happens for all modules, so it is unlikely that this is the reason for your error.
Even after using the "BulkEdit_Support.xla" addin, this is true; because the ASCII file supports "carriage return" code & generally this data is copy-paste from other excel file, which is not ASCII file.
Easiest option is to use the last column in bulk edit file as "Boolean" or "Numeric" parameter.
Any way, The number of times you will see the error is same as the number of errors you have in the database descriptions. As Youssef has suggested, correct the bulk edit data file to find & remove these "unwanted characters" & re-import.
One of the reasons of this issue is use of foreign languages in the descriptions. Many characters are not supported, if taken from different language. Also check if there are any <'s> or backslashes <\> in the descriptions. These characters can be easily missed while checking in the descriptions, so you can use the find tool in Excel or write a simple micro, if you want.
I agree that it is definitely more the "client" vb function as the issue than the "server"
(Database), but the vb function is hidden and part of the product.
There are ways around that, but will it play into the future? I say fix the parameters, roll your own routine, or remove the button from the toolbar.
Yes, I found all apostrophes (there were 4) and removed them. It helped clean up my database, but didn't fix the issue.
I had been performing some bulk edits over the last few days. That's probably the issue. I'll check the files and get back with you on what I find.
In reply to AdrianOffield:
Adrian, when I edit the bmpTagSearch button in the toolbar, I get the frszTagOpenForm function. If you right-click and select 'definition' you get 'Can't Display Hidden Procedure'. This is what I meant by the function is hidden. Do you have a different experience?