In Release 2007.5 it was possible to change the value of the TRACE_TO_TRACE constraint with the "SetStringValue"-function.
In Release 2007.7 this function results in a CES crash!!!
Attached is an example script using the "SetStringValue"-function. Maybe there exists another method to change this value
but nothing we tried worked so far.
Dear John,
thank you very much for this hint. It works, but the changed values are not saved in the CES database. So when CES is closed and reopened all constraints changed with the
DeleteConstraint and AddConstraint Method show a "0"!
What can I do to keep the new values?
Kind regards,
Christian
Hi Christian,
I did not see this behavior in my testing. You are running 2007.7, right? Does it matter whether CES was invoked from DxDesigner or Expedition? Could you post or email a database that shows this problem? Maybe there are some clues in the logfiles.
John
Dear John,
my problem occurs no matter whether the constraints import is done in DxD-CES or Expedition-CES. After my script finished the values seem to be okay,
but when I close and reopen CES a zero value appears in the changed cells instead.
Since the zipped project is bigger than 5MB I will send you the file via ftp.
Kind regards,
Christian
Dear John,
sorry, but I tried to send you the testcase files via mail. I hope this works since I dont know whether you get mails sent to
Regards,
Christian
My email address is in my profile. I don't get emails that are sent to community_admin.
John
Hi John,
have you already done some investigation? In the meantime I succeded in programming a script that
works in 2007.7 and may be in 7.9 also.
The trick is to catch the constraints with default values. To do this I use the ConstraintDef object:
set condef = <sheet>.Columns(<constraint>).ConstraintDef
Then the default value of the constraint is:
defval = condef.Default
For each constraint with default value I use your script to delete the constraint and add it again.
For the other constraints the SetStringValue-method works well.
At the moment a test is running whether the same script works in 7.9 also. If not some more
investigation will be necessary.
Hi Christian,
I am afraid that I have not done any further investigation yet.
As I pointed out earlier, the underlying defect was fixed in 7.9, so the workaround should not be necessary, but I am glad that you have a solution for both versions.
John
Hi Christian,
The SetStringValue method returns a boolean, so you should not use the "Set" statement. Make this change on line 16:
Setchanged = oconstraint.SetStringValue(CStr(value), CLng(35))There is also a bug, which has been fixed in 7.9, that causes a crash when editing default constraint values. If you modify the constraint before running your script, you will see no crash.
You can work around this bug by deleting the constraint, adding the constraint, then setting the value, like this:
John