S D
accessd667 at yahoo.com
Mon Apr 5 02:43:21 CDT 2004
The bug was that users used diff regional settings (dutch and US) and with short dates that resulted in problems 6-1-2003 is in Holland 6 january, in US its june first.... I set the format property for all date fields to dd-mmm-yyyy Sander Gustav Brock <gustav at cactus.dk> wrote: Hi Sander Well - but what is the bug and how did you solve it? /gustav > Hi gustav, > I've solved the problem. Twas a nasty one. > but euh try it if you want. create a table with a date field like below and run the query...no go! > Thanx anyway. > Sander > Gustav Brock wrote: > Hi Sander > Your "stupid" test is correct as it sorts DESC on a string. > Try this which I think is what Bert-Jan has in mind: > SELECT DISTINCT > Format([TblArbo].[Datum], "dd-mmm-yyyy") > FROM > TblArbo > ORDER BY > [TblArbo].[Datum] DESC; > /gustav >> I've got a combobox based on a query: >> SELECT DISTINCT [TblArbo].[Datum] >> FROM TblArbo >> ORDER BY [TblArbo].[Datum] DESC; >> Resulted in: >> 01-10-2003 >> 02-09-2003 >> 21-08-2001 >> The user asked if this could be printed in the following format: dd-mmm-yyyy >> No problem, says stupid me: >> SELECT DISTINCT Format([TblArbo].[Datum],"dd-mmm-yyyy") >> FROM TblArbo >> ORDER BY Format([TblArbo].[Datum],"dd-mmm-yyyy") DESC; >> But now the ORDER BY ONLY checks the DD part?!?!?!?! >> So this results in: >> 21-08-2001 >> 02-09-2003 >> 01-10-2003 >> ?!!??! What kind of nonsense is this? -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com --------------------------------- Do you Yahoo!? Yahoo! Small Business $15K Web Design Giveaway - Enter today