If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Date issue! Please help
Hello,
I have a problem when convert program from dBaseIII to Access. The date field that is mm/dd/yy is okay if that were 19XX for example 1993,1998, 1999 but the problem happen when the year is 2000, 2001 and so on these years will appear as 1900, 1901, 1902 and so on. I get one suggestion from Doug Steele that a query update and DateAdd("yyyy",100, [DateField])) but it will also change the correct years. I want to correct those years that appear not correct only. I do not know how to program it. I posted this yesterday. Are there any suggestion that may help to code it. Thanks in Advance, Le Tran |
#2
|
|||
|
|||
Date issue! Please help
On Thu, 13 May 2004 08:01:30 -0700, "Le Tran"
wrote: Hello, I have a problem when convert program from dBaseIII to Access. The date field that is mm/dd/yy is okay if that were 19XX for example 1993,1998, 1999 but the problem happen when the year is 2000, 2001 and so on these years will appear as 1900, 1901, 1902 and so on. I get one suggestion from Doug Steele that a query update and DateAdd("yyyy",100, [DateField])) but it will also change the correct years. I want to correct those years that appear not correct only. I do not know how to program it. I posted this yesterday. Are there any suggestion that may help to code it. Thanks in Advance, Le Tran You'll have to determine which dates are correct and incorrect. One thing to check is to see if 1930 is the breakpoint (that's where Access switches centuries on two-digit years) - it might be different. You could then use a criterion of #1/1/1930# as a criterion. If your data could validly contain some records from 1903 and others from 2003 (I've got a friend born in 1897 so it's a real problem for birthdates!) you may be stuck with a genuine Y2K bug. Does your dBase data contain actual dates, or just text fields with two-digit years? Note that Access Date/Time values are stored as Double Float numbers, and cover a range from 100 AD through 9999 AD - you can set the Format to display four digit years, and Access will not by itself move centuries on you. John W. Vinson[MVP] Come for live chats every Tuesday and Thursday http://go.compuserve.com/msdevapps?loc=us&access=public |
#3
|
|||
|
|||
Date issue! Please help
Hi John,
this program is just about 15 years and store information about chemicals. Therefore, I just concern about those chemicals that we input from 2000 upto now only. Please baby step to help I do not familiar with Access just switch from dBase. Or explain more clearly so that I can do by myself because of my English. Thank you very much. Le Tran |
Thread Tools | |
Display Modes | |
|
|