None of the tables that are causing this error for us contain bigints,
memos or booleans.
./peter
Peter T. Bense - Teradata Certified Professional
(ptbense@gwm.sc.edu) - 803-777-9476
Database Administrator/Webmaster
Prevention Research Center
University of South Carolina
>>> Steve Backman <earlysteve@earthlink.net> 03/06/05 6:50 AM >>>
If its field types, its not from having access translate pg bigints to
decimals, because we tried that.
it seems to translate pg text to memo ok. At least for me now, its
translating boolean to char1, but its hard to see that as fatal.
