I have also been experiencing similar errors in 4.0.3. I've found that I
can stop or change the integer value errors by changes in workflow execution
order, especially table field refreshes (even when the table field has no
common fields or query sources with the affected fields). DDE commands to
Word fail intermittently, although the worst can be avoided by opening Word
and the required document template manually before running the report macro.
I had a ticket open with Remedy (RQST00000325262) but was unable to give
them enough to go on since I cannot recreate the problems in a test
scenario. I would have to send them my entire set of defs and data, I
think. Most of these errors show up in my Control Panel form, which is very
complex and has links to virtually all the rest of my forms and data. I
have noticed a strong correlation with macros spawning further active links.
i.e. a macro with commonly used workflow is set to execute on return on a
given field, and is then called as a subroutine from other active links via
a macro using current window action 10,2.

I would be interested in any info you have on these problems, and
workarounds you have found.

And despite all our minor problems, Happy New Year to All!

Dann Cox
Systems Support Specialist
School District 68, Nanaimo, B.C. Canada
mailto:dcox@sd68.bc.ca
(250) 741-5270 fax: (250) 754-6511


-----Original Message-----
From: Schoner, Brian [mailto:BRIAN.SCHONER@FIRSTUNION.COM]
Sent: Friday, December 31, 1999 6:34 AM
To: ARSLIST@LISTSERV.VISTAIT.COM
Subject: Re: Remedy 4.0.3 "performance enhancements" and Happy New Ye


However, the patch has introduced some new problems on Windows NT machines.
We
are seeing a lot of error messages about integer values being too large or
too
small when they're well within the field's limits, and sometimes when the
field
referenced isn't even an integer field. We've also run into some DDE
problems
under NT with the new client.


To Unsubscribe send e-mail to:
body of text is: unsubscribe arslist