Francis Harvey
HARVEYF1 at WESTAT.com
Mon Jun 14 12:06:03 CDT 2004
John, According to BOL, it doesn't. Your date string is in a format that SQL Server recognized as a date string. Even better, it is internationalized, so the conversion can't be done incorrectly. Again, the assumption is that DateOfBirth is a datetime variable. Just drop the CONVERT. I am curious to know how SQL Server threw this in. Was it something to do with an ADP or were you converting a database to MSDE? I hadn't seen this problem before and would like to avoid it. Silly Microsoft, always adding unnecessary parenthesis, functions, etc. Francis R Harvey III WB 303, (301)294-3952 harveyf1 at westat.com > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby > Sent: Sunday, June 13, 2004 12:12 AM > To: 'Access Developers discussion and problem solving' > Subject: RE: [AccessD] Date syntax in SQL Server > > > But why does it need the convert? Just part of SQL Server? > > John W. Colby > www.ColbyConsulting.com > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of vchas > Sent: Sunday, June 13, 2004 12:00 AM > To: 'Access Developers discussion and problem solving' > Subject: RE: [AccessD] Date syntax in SQL Server > > > In sql dates are treated like strings, use single quotes not # > > Good Luck > > V > www.vinniechas.com <snip>