By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
444,155 Members | 2,518 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 444,155 IT Pros & Developers. It's quick & easy.

datetime field overflow (year 1899)

P: n/a
Hi,

I'm getting the datetime field overflow error using odbc to connect to an
sql database from access. This happens when I try to enter the date
13/01/1899. It did happen when using smalldatetime, which apparently does
have that problem of only going as far back as 1900, but since changing to
datetime the error still pops up.

Is there anything I can do?

Cheers,
Chris
Nov 12 '05 #1
Share this Question
Share on Google+
6 Replies


P: n/a
After you change the datatype to datetime in SQL Server you need to refresh
the linked table in Access.

Terry
"Not Me" <No****@faker.fake.fa.ke> wrote in message
news:bv**********@ucsnew1.ncl.ac.uk...
Hi,

I'm getting the datetime field overflow error using odbc to connect to an
sql database from access. This happens when I try to enter the date
13/01/1899. It did happen when using smalldatetime, which apparently does
have that problem of only going as far back as 1900, but since changing to
datetime the error still pops up.

Is there anything I can do?

Cheers,
Chris

Nov 12 '05 #2

P: n/a
Thanks, but that didn't work :o( still get the conversion errors

Cheers,
Chris
"Terry Kreft" <te*********@mps.co.uk> wrote in message
news:aI********************@karoo.co.uk...
After you change the datatype to datetime in SQL Server you need to refresh the linked table in Access.

Terry
"Not Me" <No****@faker.fake.fa.ke> wrote in message
news:bv**********@ucsnew1.ncl.ac.uk...
Hi,

I'm getting the datetime field overflow error using odbc to connect to an sql database from access. This happens when I try to enter the date
13/01/1899. It did happen when using smalldatetime, which apparently does have that problem of only going as far back as 1900, but since changing to datetime the error still pops up.

Is there anything I can do?

Cheers,
Chris


Nov 12 '05 #3

P: n/a
Strange it worked here.

Which version of Access / SQL are you using ?

Terry
"Not Me" <No****@faker.fake.fa.ke> wrote in message
news:bv**********@ucsnew1.ncl.ac.uk...
Thanks, but that didn't work :o( still get the conversion errors

Cheers,
Chris
"Terry Kreft" <te*********@mps.co.uk> wrote in message
news:aI********************@karoo.co.uk...
After you change the datatype to datetime in SQL Server you need to refresh
the linked table in Access.

Terry
"Not Me" <No****@faker.fake.fa.ke> wrote in message
news:bv**********@ucsnew1.ncl.ac.uk...
Hi,

I'm getting the datetime field overflow error using odbc to connect to an sql database from access. This happens when I try to enter the date
13/01/1899. It did happen when using smalldatetime, which apparently does have that problem of only going as far back as 1900, but since
changing to datetime the error still pops up.

Is there anything I can do?

Cheers,
Chris



Nov 12 '05 #4

P: n/a
SQL 8, Access 2002.... I guess the problem must be hiding someplace else..

cheers,
Chris
"Terry Kreft" <te*********@mps.co.uk> wrote in message
news:Ls********************@karoo.co.uk...
Strange it worked here.

Which version of Access / SQL are you using ?

Terry
"Not Me" <No****@faker.fake.fa.ke> wrote in message
news:bv**********@ucsnew1.ncl.ac.uk...
Thanks, but that didn't work :o( still get the conversion errors

"Terry Kreft" <te*********@mps.co.uk> wrote in message
news:aI********************@karoo.co.uk...
After you change the datatype to datetime in SQL Server you need to

refresh
the linked table in Access.

"Not Me" <No****@faker.fake.fa.ke> wrote in message
news:bv**********@ucsnew1.ncl.ac.uk...
> Hi,
>
> I'm getting the datetime field overflow error using odbc to connect
to an
> sql database from access. This happens when I try to enter the date
> 13/01/1899. It did happen when using smalldatetime, which
apparently does
> have that problem of only going as far back as 1900, but since

changing
to
> datetime the error still pops up.
>
> Is there anything I can do?

Nov 12 '05 #5

P: n/a
SQL Server 2000 and Access XP, those are the same versions I used to test
this.

Hmm, strange.

I'd suggest you go back and check through the steps again.

Make sure the field type on SQL is now datetime
Go into Access and use the Tools/Database Utilities/Linked Table Wizard
to refresh the link
Test whether you can add the data through the table
Terry
"Not Me" <No****@faker.fake.fa.ke> wrote in message
news:c0**********@ucsnew1.ncl.ac.uk...
SQL 8, Access 2002.... I guess the problem must be hiding someplace else..

cheers,
Chris
"Terry Kreft" <te*********@mps.co.uk> wrote in message
news:Ls********************@karoo.co.uk...
Strange it worked here.

Which version of Access / SQL are you using ?

Terry
"Not Me" <No****@faker.fake.fa.ke> wrote in message
news:bv**********@ucsnew1.ncl.ac.uk...
Thanks, but that didn't work :o( still get the conversion errors

"Terry Kreft" <te*********@mps.co.uk> wrote in message
news:aI********************@karoo.co.uk...
> After you change the datatype to datetime in SQL Server you need to
refresh
> the linked table in Access.
>
> "Not Me" <No****@faker.fake.fa.ke> wrote in message
> news:bv**********@ucsnew1.ncl.ac.uk...
> > Hi,
> >
> > I'm getting the datetime field overflow error using odbc to connect
to
an
> > sql database from access. This happens when I try to enter the
date > > 13/01/1899. It did happen when using smalldatetime, which

apparently does
> > have that problem of only going as far back as 1900, but since

changing
to
> > datetime the error still pops up.
> >
> > Is there anything I can do?


Nov 12 '05 #6

P: n/a
I think the SQL requires US-format for dates: mm/dd/yyyy and it may be
choking up on a thirteenth month.

Larry Linson
Microsoft Access MVP

"Not Me" <No****@faker.fake.fa.ke> wrote in message
news:c0**********@ucsnew1.ncl.ac.uk...
SQL 8, Access 2002.... I guess the problem must be hiding someplace else..

cheers,
Chris
"Terry Kreft" <te*********@mps.co.uk> wrote in message
news:Ls********************@karoo.co.uk...
Strange it worked here.

Which version of Access / SQL are you using ?

Terry
"Not Me" <No****@faker.fake.fa.ke> wrote in message
news:bv**********@ucsnew1.ncl.ac.uk...
Thanks, but that didn't work :o( still get the conversion errors

"Terry Kreft" <te*********@mps.co.uk> wrote in message
news:aI********************@karoo.co.uk...
> After you change the datatype to datetime in SQL Server you need to
refresh
> the linked table in Access.
>
> "Not Me" <No****@faker.fake.fa.ke> wrote in message
> news:bv**********@ucsnew1.ncl.ac.uk...
> > Hi,
> >
> > I'm getting the datetime field overflow error using odbc to connect
to
an
> > sql database from access. This happens when I try to enter the
date > > 13/01/1899. It did happen when using smalldatetime, which

apparently does
> > have that problem of only going as far back as 1900, but since

changing
to
> > datetime the error still pops up.
> >
> > Is there anything I can do?


Nov 12 '05 #7

This discussion thread is closed

Replies have been disabled for this discussion.