Group:  Microsoft Access ยป microsoft.public.access.devtoolkits
Thread: Datetime field overflow on new record only.

DotNetBag
.NET Development Newsgroups

HTVi
TV Discussion Newsgroups

Our Hot Pick: Rising Antivirus 2006 - Certified by TUV & Checkmark! Get 10% discount by entering this coupon code: ONDISCOUNT10
Rising Antivirus 2006

Datetime field overflow on new record only.
janetb 03.03.2006 21:40:29
Using AccessXP as front-end to sql2000 backend. Have .net pages
adding/updating/changing fine. But, on Access form when adding a new record,
I get:

ODBC call failed. Microsoft ODBC SQL Driver. Fractional truncation (#0)
DateTime field overflow (#0)

But, if I'm updating a record that's already been entered and just change
the date field in question from
3/15/2006 06:30:00 pm to 3/15/2006 06:45:00 pm
there's no error.

Any Help?

Thanks,
Janet
RE: Datetime field overflow on new record only.
janetb 06.03.2006 14:41:27
Found the error - it was an incorrect default setting in one of the date
fields. Interesting that Access picked up 0 as a default setting on a date
field?

"janetb" wrote:

[Quoted Text]
> Using AccessXP as front-end to sql2000 backend. Have .net pages
> adding/updating/changing fine. But, on Access form when adding a new record,
> I get:
>
> ODBC call failed. Microsoft ODBC SQL Driver. Fractional truncation (#0)
> DateTime field overflow (#0)
>
> But, if I'm updating a record that's already been entered and just change
> the date field in question from
> 3/15/2006 06:30:00 pm to 3/15/2006 06:45:00 pm
> there's no error.
>
> Any Help?
>
> Thanks,
> Janet
Re: Datetime field overflow on new record only.
"Douglas J. Steele" <NOSPAM_djsteele[ at ]NOSPAM_canada.com> 06.03.2006 22:36:20
Dates are just numbers to Access (specifically, 8 byte floating point
numbers where the integer portion represents the date as the number of days
relative to 30 Dec, 1899, and the decimal portion represents the time as a
fraction of a day). 0 is the usual default for numeric fields.

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no private e-mails, please)


"janetb" <janetb[ at ]discussions.microsoft.com> wrote in message
news:1B01D5AA-0566-415F-8368-E1669E1DE332[ at ]microsoft.com...
[Quoted Text]
> Found the error - it was an incorrect default setting in one of the date
> fields. Interesting that Access picked up 0 as a default setting on a
> date
> field?
>
> "janetb" wrote:
>
>> Using AccessXP as front-end to sql2000 backend. Have .net pages
>> adding/updating/changing fine. But, on Access form when adding a new
>> record,
>> I get:
>>
>> ODBC call failed. Microsoft ODBC SQL Driver. Fractional truncation (#0)
>> DateTime field overflow (#0)
>>
>> But, if I'm updating a record that's already been entered and just change
>> the date field in question from
>> 3/15/2006 06:30:00 pm to 3/15/2006 06:45:00 pm
>> there's no error.
>>
>> Any Help?
>>
>> Thanks,
>> Janet


Home | Search | Terms | Imprint | Contact
Newsgroups Reader - provided by WiredBox.Net