Nicholson, Karen
cyx5 at cdc.gov
Tue Sep 28 13:58:50 CDT 2004
Not this puppy! The ODBC driver is from some company called pervasive.com. -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte Foust Sent: Tuesday, September 28, 2004 11:34 AM To: Access Developers discussion and problem solving Subject: RE: [AccessD] Access/SQL Dates SQL Server uses single quotes around date values. Charlotte Foust -----Original Message----- From: Heenan, Lambert [mailto:Lambert.Heenan at aig.com] Sent: Monday, September 27, 2004 8:19 AM To: 'Access Developers discussion and problem solving'; 'Nicholson, Karen' Subject: RE: [AccessD] Access/SQL Dates Very probably I am wrong as I've not yet had the joy of dealing with SQL server, but is it not the case that the date delimiting character in SQL Server is the percentage symbol (%) not pound or hash (#)? Lambert > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [SMTP:accessd-bounces at databaseadvisors.com] On Behalf Of Nicholson, Karen > Sent: Monday, September 27, 2004 8:19 AM > To: Access Developers discussion and problem solving > Subject: RE: [AccessD] Access/SQL Dates > > Interesting. The SQL backend structure can not be changed as it is > proprietary. Yikes. > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Mike & > Doris Manning > Sent: Monday, September 27, 2004 7:27 AM > To: 'Access Developers discussion and problem solving' > Subject: RE: [AccessD] Access/SQL Dates > > > I ran into this problem when I used smalldatetime in the table as the > data type instead of datetime. To be honest, I was in a hurry and > didn't have > time to figure out why it was happening. I just changed from > smalldatetime > to datetime and the problem went away. I've never used smalldatetime > since > then. > > Doris Manning > Database Administrator > Hargrove Inc. > www.hargroveinc.com > > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Nicholson, > Karen > Sent: Monday, September 27, 2004 6:33 AM > To: accessd at databaseadvisors.com > Subject: [AccessD] Access/SQL Dates > > > I have an Access front-end and am querying an SQL backend. When > putting in a select statement in the query, all is fine if I specify a > date of say, less than today or <date()... However, if I try to > specify a particular date, I get an sql overflow error. The syntaxes > I have tried > include: <#9/27/2004# <'9/27/2004' <'20040927'. Any clues? Thanks. > > Karen Nicholson > National Laboratory > Xerox Global Services > > > -- > _______________________________________________ > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > > -- > _______________________________________________ > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > -- > _______________________________________________ > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com