>>>>>Your integers have only 32 bits, numbered from 0 to 31. You overstepped.
>>>>>
>>>>>(and this is not the bittest question in the world - I've seen bitter...)
>>>>
>>>>I suppose that this function cannot be applied to BigInt type, which if I understand correctly, has 64 bits. No?
>>>
>>>VFP doesn't do 64 bit integers. If such a number is encountered, it is automatically converted as IEEE float, with standard 15,5 significant digits.
>>
>>A follow up question, if you don't mind. Does it mean then, when using SQL Server as database for VFP application, using the Bigint type column does not make much sense? Since VFP only uses 32 bit integers.
>
>Assuming you have a need for such integers (I never had), the values you'd get in VFP may be too big to fit a 32 bit integer, so in a view/cursor you'd have to map it to something like a n(19,0) or whatever is the limit or necessary size. But then when you try to manipulate those numbers in variables, you'd run into the limitation of 32-bit IEEE floats, the 15,5 significant digits. Just try
>?1000000000000555+1000000000000555
>?10000000000000555+10000000000000555
>?100000000000000555+100000000000000555
>and you'll find that the result ends with 1110 in first two cases, but ends with 1100 in the last. That's that limitation, the lowest digits on the lower end get lost.
>
>So, the answer is the usual "it depends". This time, depends on what you need to do.

The only reason I was thinking of using big integers is that I thought I would be able to use them with Bittest() function. But, since Bitest() does not accept numbers greater than 31, I won't be using Bigint in SQL Server.
Thank you.