Re: unsigned integer in MS Access
- From: "Brendan Reynolds" <brenreyn@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 15 Sep 2005 11:54:21 +0100
Which unsigned integer are we talking about? .NET has UInt16, UInt32, and
UInt64. A UInt16 has a maximum value of 65535, and will fit happily in a Jet
Integer field. A UInt32 has a maximum value of 4294967295, and will require
Single, Double, Decimal or Currency. A UInt64 has a maximum value of
18446744073709551615, and will require Single or Double, with possible loss
of precision. If you don't need to perform any numeric operations on the
data, you could store it in a text field.
--
Brendan Reynolds (MVP)
"Davor" <Davor@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:FD8CE242-298C-4D4F-8052-72ADA1AC7785@xxxxxxxxxxxxxxxx
> Hello
>
> I am using Access 2002, and a 2000 Compatible DB. I am importing data that
> is originaly an unsigned integer (.NET) (this means long in Access) Thing
> i
> would like to do is let access accept unisgned integers, but i don't know
> how. Is it even possible?
>
> Converting uInt to signed is not realy an option as I have to sum all the
> imported data regulary.
>
> Greets
> Davor
.
- Prev by Date: Re: unsigned integer in MS Access
- Next by Date: Re: unsigned integer in MS Access
- Previous by thread: Re: unsigned integer in MS Access
- Next by thread: Re: unsigned integer in MS Access
- Index(es):