Thanks everyone for your responses. I checked to ensure the variable cost.visible is true and it is set to a value of '1'.
If I comment out the conditional code IF COST # COST.WAS THEN - well, the new/current cost value is always redisplayed. I guess I'm just gonna have to chalk it up as a mystery. So, test for inequality it seems fails often on my development system running Windows XP Pro SP2, UV version 9.6.1.3, but the exact same code executes just fine on the actual customers server - which is where it counts of course. Their server is running Windows 2003 server, UV version 10.1.3. I didn't have this problem when the OS on my development system was Windows 2000 Pro - UV 9.6.1.3 may not be officially 'supported' on Windows XP Pro SP2 - I'll have to check the product matrix. Maybe it's time for me to do a universe upgrade on my development system (no kidding, way overdue). -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Joey Walter Sent: Wednesday, March 01, 2006 7:30 PM To: [email protected] Subject: [U2] UV: tests for inequality failing. Wide0 parameter? I'm having a problem with comparisons for equality between variables failing. Very simple code: IF COST # COST.WAS THEN IF COST.VISIBLE THEN GOSUB SHOW.COST END And I'm expecting of course for the gosub to be executed when I know for certain the variables COST and COST.WAS are not equal - but it doesn't happen. For instance the test for inequality fails when the variable COST = 1505 and variable COST.WAS = 1507. I wrote a line of code to display the OCONV'd variables and in the case mentioned above it displayed this: recalc.unit.cost; cost was 15.07 cost is 15.05 But, the subroutine to display the new cost did not get executed. Anyway, I'm guessing it's a problem with that bizarre little parameter called Wide0? I currently have it set to 0x3eb00000. Why do I have it set that way - purely because I had problems with the default setting and someone tossed me a clue and told me to try 0x3eb00000 and I never had problems since on my development machine or any other - until now. Anyone that can help me out with this? What's a reasonable/functional setting for Wide0 parameter. I don't need accuracy past six decimal places. Thanks. ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
