Ok, bud (i think may be today it is to hot ;-) ) i do not unterstand what this mean!
Do i have now to change the Field definitions on the SQL Server? Which datatype will be the right thing?


This is the mother of all the issues.

this is VFP <-> SQL data type support ( a partial list )
full -> it is ok
full* -> it would have to be right, but i'm not sure
subrange -> VFP data is a subrange of SQL data

*SQL		VFP          Exact read		Exact write	Range	Computation
**************************************************************************************
Bit           	Logical		full		full		full		full
Tiny          	Integer		full		full		full		full
Smallint      	Integer		full		full		full		full
Int           	Integer		full		full		subrange	full
Smallmoney    	Currency	full		full		full		full
Money         	Currency	full		full		subrange	full
Smalldatetime	Datetime	full		full		full		full*
Datetime       	Datetime	trunk		full		full		full*
Real		Double		approximately	approximately	full		approximately
Double		Double		full*		full*		subrange	full*
Decimal(N,M)	Numeric		full*		No		full*		approximately
* N : 1..15  M : 0..15 and M+N : 1..15

Of course, I am in your same situation,
if, for having exact sums, I must use a SQL decimal(), i'm in large difficulties.

I do not use RV or CA (why I do not trust), and I use only SPT.
For the same reason i don't write VFP computed values into my SQL Backend.

Fabio