From fuller.artful at gmail.com Mon Aug 6 20:15:56 2007 From: fuller.artful at gmail.com (Arthur Fuller) Date: Mon, 6 Aug 2007 21:15:56 -0400 Subject: [dba-SQLServer] A puzzle re: differences between 2000 and 2005 Message-ID: <29f585dd0708061815xc48a1aer423399f6ab27e89b@mail.gmail.com> I regularly use a dialog in my apps that contains a calendar and allows you to set a date range, which values are then passed to a report using InputParameters. The form works perfectly with a sql 2000 database but apparently not with a sql 2005 database. Has something changed regarding datetime fields in 2005? The forms and the InputParameters settings are identical, but I get an error in the 2005 app. It's using Access 2000 format, and otherwise runs fine in Access 2000 and 2003. The form is slick and I'd hate to stop using it. I cannot figure out what's wrong. If I have to, I'll convert the database to SQL 2000 format just so I can continue using this form, but that is less than ideal. Anybody got a clue as to why this behaviour occurs? Or alternatively, a popup calendar control known to work against a SQL 2005 database? TIA, Arthur From fhtapia at gmail.com Tue Aug 7 09:59:15 2007 From: fhtapia at gmail.com (Francisco Tapia) Date: Tue, 7 Aug 2007 07:59:15 -0700 Subject: [dba-SQLServer] A puzzle re: differences between 2000 and 2005 In-Reply-To: <29f585dd0708061815xc48a1aer423399f6ab27e89b@mail.gmail.com> References: <29f585dd0708061815xc48a1aer423399f6ab27e89b@mail.gmail.com> Message-ID: I have not had any issues with the date format for 2005, but I'm not using any pop-up forms, but I'm curious what is the expected date format in the popup control?, is the control bound? What sort of error message are you getting? -- Francisco On 8/6/07, Arthur Fuller wrote: > > I regularly use a dialog in my apps that contains a calendar and allows > you > to set a date range, which values are then passed to a report using > InputParameters. The form works perfectly with a sql 2000 database but > apparently not with a sql 2005 database. Has something changed regarding > datetime fields in 2005? The forms and the InputParameters settings are > identical, but I get an error in the 2005 app. It's using Access 2000 > format, and otherwise runs fine in Access 2000 and 2003. The form is slick > and I'd hate to stop using it. I cannot figure out what's wrong. If I have > to, I'll convert the database to SQL 2000 format just so I can continue > using this form, but that is less than ideal. > > Anybody got a clue as to why this behaviour occurs? Or alternatively, a > popup calendar control known to work against a SQL 2005 database? > > TIA, > Arthur > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > > -- -Francisco http://sqlthis.blogspot.com | Tsql and More...