"Rick Brandt" <ri*********@ho tmail.com> wrote in message news:<39******* ******@individu al.net>...
Is your ODBC driver current? I have never seen this behavior, but I have
never used the upsize wizard either.
I'm using 2000.85.1117.0 dated 4/8/2004, so fairly up-to-date though
it may not be the latest. I haven't seen any reference on Technet to
this problem. Further testing actually reduced it to the following
sequence:
- View table A in datasheet view: currency column data visible
- Close table A
- Open table B in datasheet view: currency column data invisible
(except if zero)
- Close table B
- View table A in datasheet view: currency column data invisible
!!!!
I have since tried various measures to circumvent this difficulty. I
hesitate to prescribe the following as a trusted procedure - it's too
early to talk of trust! However, I have money fields in SQL Server
which were upsized from Access currency columns, and I can see the
values from the Access front-end. What appeared to work was (1)not
selecting 'use regional settings...' when setting up the ODBC
datasource (2)choosing triggers rather than DRI for upsizing
integrity. I was a bit nonplussed to find that the triggers were not
generated if the wizard was run on the Access front-end, only if on
the back-end. This meant the automatic relinking that the wizard does
was on the wrong database and had to be rectified by hand which could
be tiresome for a large database.
Hope this of use to other benighted upsizers out there!
Dave