Yep ... glad I'm not the only one to have noticed the problem :) I
thought our system was going crazy because some consolidation data was
incorrect and yet there were no posts on the list about it.
In any case, I'm currently writing my own consolidation routines now in
Visual Basic. I'm practically done now. The only vexing question I have
comes from the trace of the SQL calls during a test consolidation here.
After every single "INSERT INTO Charges" statement, there is a following
statement:
"Select LastIdentity=@@IDENTITY"
OK, so this selects the identity of the last row inserted into the charges
table, but what is this used for?? I can't seem to find any reason for it.
Am I overlooking something really simple??
I'd appreciate any answer that anyone can provide.
I can mail anyone the code for my consolidation routine if they want it.
Just mail me and I'll send it when it's ready (any day now :).
--------------------------------------#------------------------------------
David Khoury | "Where's the KABOOM ??
Technical Manager & Comms Engineer | There was supposed to be an
dave@flex.com.au | earth shattering KABOOM!!"
http://www.flex.com.au/~dave | Marvin the Martian
--------------------------------------#------------------------------------