dbTalk Databases Forums  

Importing two digit year comma delimited dates

comp.databases.paradox comp.databases.paradox


Discuss Importing two digit year comma delimited dates in the comp.databases.paradox forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Don
 
Posts: n/a

Default Importing two digit year comma delimited dates - 05-25-2007 , 05:48 PM







I'm using Pdox9, plus 1,2,3SP's, on WinXP prof.
The .csv dates are "04/01/07".
After importing, I get 4/1/1907 or 4/1/0007 (am importing from 2 files, one
having field names in first row of data).
I am importing using the Import Data feature and not the Text Expert feature
b/c the files have 125 fields.
Win XP short date format is 4/1/2007.
BDE 5.01 settings are: 4 digit yr = TRUE; LeadingZeroD = FALSE; LeadingZeroM
= FALSE; Mode = 0; Separator = /; YearBiased = TRUE.
Is there a way to get a 2007 year after importing?
Thanks.

Reply With Quote
  #2  
Old   
Steven Green
 
Posts: n/a

Default Re: Importing two digit year comma delimited dates - 05-25-2007 , 06:01 PM






Quote:
Is there a way to get a 2007 year after importing?
sure.. scan the table and change it.. that might seem like a flippant answer
at first, but over time you'll find out that not every import value is
perfect.. changing and/or correcting is part of the game..

--
Steven Green - Waldorf Maryland USA

Diamond Software Group
http://www.diamondsg.com/main.htm
Paradox Support & Sales

Diamond Sports Gems
http://www.diamondsg.com/gemsmain.htm
Sports Memorabilia and Trading Cards




Reply With Quote
  #3  
Old   
Rick Rans
 
Posts: n/a

Default Re: Importing two digit year comma delimited dates - 05-25-2007 , 09:07 PM



Don

I think your Four Digit Year setting should be false. From the help file
-----------------------------------------------------------
FOURDIGITYEAR
Determines how the BDE treats the century portion of a date when only the
last two digits of a year are specified. If set to FALSE, the century part
of the date's year is added automatically based on its relative position in
a baseline range. If the date falls between 01/01/00 and 12/31/49, the year
is considered to be in the 21st century (05/20/22 becomes 05/20/2022). If
the date falls between 01/01/50 and 12/31/99, the date is considered as
being in the 20th century (12/08/98 becomes 12/08/1998). A TRUE setting has
no effect on dates expressed with a century (the year of a new date of
12/30/1902 remains 1902).

If set to TRUE, the year for the date is assumed to be literal (no century
digits automatically prefixed to the date). For example, a date expressed as
07/72/96 is considered to be the year 96 (0096).

FOURDIGITYEAR has an effect in such places as date literals in SQL
statements.

Default value: FALSE.
--------------------------------------------------------

HTH - Rick

"Don" <donn (AT) princetonair (DOT) com> wrote

Quote:
I'm using Pdox9, plus 1,2,3SP's, on WinXP prof.
The .csv dates are "04/01/07".
After importing, I get 4/1/1907 or 4/1/0007 (am importing from 2 files,
one
having field names in first row of data).
I am importing using the Import Data feature and not the Text Expert
feature
b/c the files have 125 fields.
Win XP short date format is 4/1/2007.
BDE 5.01 settings are: 4 digit yr = TRUE; LeadingZeroD = FALSE;
LeadingZeroM
= FALSE; Mode = 0; Separator = /; YearBiased = TRUE.
Is there a way to get a 2007 year after importing?
Thanks.



Reply With Quote
  #4  
Old   
don
 
Posts: n/a

Default Re: Importing two digit year comma delimited dates - 05-26-2007 , 12:52 PM




"Rick Rans" <rick.rans (AT) canada (DOT) com> wrote:
Quote:
Don

I think your Four Digit Year setting should be false. From the help file
-----------------------------------------------------------
FOURDIGITYEAR
Determines how the BDE treats the century portion of a date when only the

last two digits of a year are specified. If set to FALSE, the century part

of the date's year is added automatically based on its relative position
in
a baseline range. If the date falls between 01/01/00 and 12/31/49, the year

is considered to be in the 21st century (05/20/22 becomes 05/20/2022). If

the date falls between 01/01/50 and 12/31/99, the date is considered as

being in the 20th century (12/08/98 becomes 12/08/1998). A TRUE setting
has
no effect on dates expressed with a century (the year of a new date of
12/30/1902 remains 1902).

If set to TRUE, the year for the date is assumed to be literal (no century

digits automatically prefixed to the date). For example, a date expressed
as
07/72/96 is considered to be the year 96 (0096).

FOURDIGITYEAR has an effect in such places as date literals in SQL
statements.

Default value: FALSE.
--------------------------------------------------------

HTH - Rick

"Don" <donn (AT) princetonair (DOT) com> wrote in message
news:465767b1$1 (AT) pnews (DOT) thedbcommunity.com...

I'm using Pdox9, plus 1,2,3SP's, on WinXP prof.
The .csv dates are "04/01/07".
After importing, I get 4/1/1907 or 4/1/0007 (am importing from 2 files,

one
having field names in first row of data).
I am importing using the Import Data feature and not the Text Expert
feature
b/c the files have 125 fields.
Win XP short date format is 4/1/2007.
BDE 5.01 settings are: 4 digit yr = TRUE; LeadingZeroD = FALSE;
LeadingZeroM
= FALSE; Mode = 0; Separator = /; YearBiased = TRUE.
Is there a way to get a 2007 year after importing?
Thanks.


-----------------

I changed only the FOURDIGITYEAR to FALSE & now a 01/01/07 comma delimited
date imports as an alphanumeric 01/01/07. After changing the field to a Date
format, it appears as 1/1/2007.

Which Help file did you use? I couldn't find your text in Pdox9 Help.

Thanks much for the assistance.

Don


Reply With Quote
  #5  
Old   
Rick Rans
 
Posts: n/a

Default Re: Importing two digit year comma delimited dates - 05-26-2007 , 04:57 PM



The help file in BDE administrator. When looking at the System-> Formats ->
Date settings just press F1 for help.

Rick

"don" <donn (AT) princetonair (DOT) com> wrote

Quote:
"Rick Rans" <rick.rans (AT) canada (DOT) com> wrote:
Don

I think your Four Digit Year setting should be false. From the help file
-----------------------------------------------------------
FOURDIGITYEAR
Determines how the BDE treats the century portion of a date when only the

last two digits of a year are specified. If set to FALSE, the century part

of the date's year is added automatically based on its relative position
in
a baseline range. If the date falls between 01/01/00 and 12/31/49, the
year

is considered to be in the 21st century (05/20/22 becomes 05/20/2022). If

the date falls between 01/01/50 and 12/31/99, the date is considered as

being in the 20th century (12/08/98 becomes 12/08/1998). A TRUE setting
has
no effect on dates expressed with a century (the year of a new date of
12/30/1902 remains 1902).

If set to TRUE, the year for the date is assumed to be literal (no century

digits automatically prefixed to the date). For example, a date expressed
as
07/72/96 is considered to be the year 96 (0096).

FOURDIGITYEAR has an effect in such places as date literals in SQL
statements.

Default value: FALSE.
--------------------------------------------------------

HTH - Rick

"Don" <donn (AT) princetonair (DOT) com> wrote in message
news:465767b1$1 (AT) pnews (DOT) thedbcommunity.com...

I'm using Pdox9, plus 1,2,3SP's, on WinXP prof.
The .csv dates are "04/01/07".
After importing, I get 4/1/1907 or 4/1/0007 (am importing from 2 files,

one
having field names in first row of data).
I am importing using the Import Data feature and not the Text Expert
feature
b/c the files have 125 fields.
Win XP short date format is 4/1/2007.
BDE 5.01 settings are: 4 digit yr = TRUE; LeadingZeroD = FALSE;
LeadingZeroM
= FALSE; Mode = 0; Separator = /; YearBiased = TRUE.
Is there a way to get a 2007 year after importing?
Thanks.


-----------------

I changed only the FOURDIGITYEAR to FALSE & now a 01/01/07 comma delimited
date imports as an alphanumeric 01/01/07. After changing the field to a
Date
format, it appears as 1/1/2007.

Which Help file did you use? I couldn't find your text in Pdox9 Help.

Thanks much for the assistance.

Don



Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.