I think this was because of an MS Access component. MS Access didn't recognise BIGINT at the time (2000).
The NUMERICS are everywhere, there have been no problems with them to date that I'm aware of.
FYI, this old thread was revived because rchantler recently posted a similar but MUCH simpler case - it is a much better test case for this problem: