Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Bugs with literal double-precision floating-point number
Message
De
24/11/2003 12:23:20
 
 
À
24/11/2003 09:31:01
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Divers
Thread ID:
00852922
Message ID:
00852984
Vues:
11
4. Question.

QUESTION: for write on VFP and SQL Server 3.120000000000000E140 which literal I must write

Now i compare with SQL Server
? 3.119999999999971027E140 && 3.119999999999990...0E+140 SQL Server write 3.1199999999999709E+140
? 3.119999999999971028E140 && 3.120000000000000...0E+140 SQL Server write 3.1199999999999709E+140
? 3.119999999999976379E140 && 3.120000000000010...0E+140 SQL Server write 3.1199999999999764E+140
? 3.119999999999987900E140 && 3.120000000000020...0E+140 SQL Server write 3.1199999999999878E+140
? 3.119999999999998108E140 && 3.120000000000030...0E+140 SQL Server write 3.1199999999999979E+140
? 3.120000000000009659E140 && 3.120000000000040...0E+140 SQL Server write 3.1200000000000098E+140
This is a important bug: VFP conversion routine of literal dfpn have a error and shift the value.

If you want input 3.120000000000000E140 , is necessary write this literal:
x = 3.119999999999975E140  <-- this literals put 3.120000000000000E140 on x
For SQL Server support question:
- literal they are not interchanging
x = literal
sqlexec(.... =?m.x... ')
it can give turns out different result by
sqlexec(.... =literal )
For SQL Server double data stored and read on VFP i haven't found problem ( till now )

Fabio
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform