>I'll give it another shot. I tried the B(16) in the DBSetprop as you showed below but in my DBCX it still show B with a length of 8 ( whatever that means ) and Binary = .f.


That is correct - the 8 refers to the number of bytes used to store the value in memory or in the table

>They just used float for everything, including fields that would go into the millions but with only 2 or 3 decimals and other fields with values that would never be more than 1 but could go 10 decimals.)
>
>What would be the proper data types in SQL to do the cast on the sql select in the remote view for those two cases so they would make sense to VFP?

In that case I would prefer b(16), ie max 16 digits of precision but the max value is around 8.9884656743115E307 - for the millions


You may also change that data type to N(xxx, yyy) depending on the case
field - millions but with only 2 or 3 decimals
- never be more than 1 but could go 10 decimals.