Are you on the 3.1.0.6 client? I had the same problem. A quick upgrade to
3.1.0.7 fixed it. This was a known problem on 3.1.0.6, took support all of
3 seconds to tell me, after I had spent 3 hours trying to find the data.
Of 4 systems at that client level, only one showed the problem. Weird,
bad, but weird.
Nick Cassimatis
nickpc AT us.ibm DOT com
If you don't have the time to do it right the first time, where will you
find the time to do it again?
|
