dbTalk Databases Forums  

Date format problem

comp.databases.paradox comp.databases.paradox


Discuss Date format problem in the comp.databases.paradox forum.



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

Default Date format problem - 07-24-2006 , 09:39 AM






I'm importing a csv file into pdoxdos 4.5. Inspecting the csv file in a text
editor, some typical lines look like this:

201432,JELLO STRAWBERRY,07/17/06,08/12/06,5.04,0,803957
201435,JELLO CHERRY GELATIN,07/17/06,08/12/06,5.04,0,803957
201441,JELLO ORANGE GELATIN,07/17/06,08/12/06,5.04,0,803957
201442,JELLO STRAWBERRY BANANA,07/17/06,08/12/06,5.04,0,803957

Notice that the dates in those lines are intact. But, when they're imported
into a pdox table, they ended up showing with problem in the year figure,
such as 7/17/6. Double checking the table structure, it **IS** formated as
"D" in the two date fields.

Instead of using append delimited, bringing data into a table that's already
formatted, I tried importing into a fresh table. The dates show correctly.
BUT...when I inspect the structure, I find that pdox has chosen A8 for the
date fields.

Why won't the first table show the dates correctly?



Reply With Quote
  #2  
Old   
Michael Kennedy
 
Posts: n/a

Default Re: Date format problem - 07-24-2006 , 12:58 PM






Joe,

Maybe you've a Y2K issue - in general, PDoxDOS treats a 2-digit year as
being in the 19xx century. So, it's possible that your xx/xx/06 dates are
being imported as xx/xx/1906, and then the app is unhappy.

If this is the cause, you'll need to change the behaviour of PDoxDOS to be a
bit smarter, or maybe try changing the years in the CSV file from 06 to
2006.

All these matters were covered in extreme detail at the Y2K time - I reckon
there's still a lot of those Y2K notes on my website -
www.KennedySoftware.ie.

If not Y2K, you'll need to explain to us what you mean by "problem in the
year figure"

- Mike


"JoeSpareBedroom" <dishborealis (AT) yahoo (DOT) com> wrote

Quote:
I'm importing a csv file into pdoxdos 4.5. Inspecting the csv file in a
text editor, some typical lines look like this:

201432,JELLO STRAWBERRY,07/17/06,08/12/06,5.04,0,803957
201435,JELLO CHERRY GELATIN,07/17/06,08/12/06,5.04,0,803957
201441,JELLO ORANGE GELATIN,07/17/06,08/12/06,5.04,0,803957
201442,JELLO STRAWBERRY BANANA,07/17/06,08/12/06,5.04,0,803957

Notice that the dates in those lines are intact. But, when they're
imported into a pdox table, they ended up showing with problem in the year
figure, such as 7/17/6. Double checking the table structure, it **IS**
formated as "D" in the two date fields.

Instead of using append delimited, bringing data into a table that's
already formatted, I tried importing into a fresh table. The dates show
correctly. BUT...when I inspect the structure, I find that pdox has chosen
A8 for the date fields.

Why won't the first table show the dates correctly?





Reply With Quote
  #3  
Old   
JoeSpareBedroom
 
Posts: n/a

Default Re: Date format problem - 07-24-2006 , 01:30 PM



Y2K - forgot all about that. You comment reminded me that we have an old
table in which we edit dates, and simply typing "7/17/04" results in
"7/17/4". But, typing "7/17", pdox adds "2006" correctly. So, I manually
edited a few lines in the CSV file to read with 4-digit year, and they
imported correctly. I'm having our customer change the format of the Excel
sheet from which the CSV files originate.

"Michael Kennedy" <Info (AT) KennedySoftware (DOT) ie> wrote

Quote:
Joe,

Maybe you've a Y2K issue - in general, PDoxDOS treats a 2-digit year as
being in the 19xx century. So, it's possible that your xx/xx/06 dates are
being imported as xx/xx/1906, and then the app is unhappy.

If this is the cause, you'll need to change the behaviour of PDoxDOS to be
a
bit smarter, or maybe try changing the years in the CSV file from 06 to
2006.

All these matters were covered in extreme detail at the Y2K time - I
reckon
there's still a lot of those Y2K notes on my website -
www.KennedySoftware.ie.

If not Y2K, you'll need to explain to us what you mean by "problem in the
year figure"

- Mike


"JoeSpareBedroom" <dishborealis (AT) yahoo (DOT) com> wrote in message
news:LY4xg.6246$Oh1.2779 (AT) news01 (DOT) roc.ny...
I'm importing a csv file into pdoxdos 4.5. Inspecting the csv file in a
text editor, some typical lines look like this:

201432,JELLO STRAWBERRY,07/17/06,08/12/06,5.04,0,803957
201435,JELLO CHERRY GELATIN,07/17/06,08/12/06,5.04,0,803957
201441,JELLO ORANGE GELATIN,07/17/06,08/12/06,5.04,0,803957
201442,JELLO STRAWBERRY BANANA,07/17/06,08/12/06,5.04,0,803957

Notice that the dates in those lines are intact. But, when they're
imported into a pdox table, they ended up showing with problem in the
year
figure, such as 7/17/6. Double checking the table structure, it **IS**
formated as "D" in the two date fields.

Instead of using append delimited, bringing data into a table that's
already formatted, I tried importing into a fresh table. The dates show
correctly. BUT...when I inspect the structure, I find that pdox has
chosen
A8 for the date fields.

Why won't the first table show the dates correctly?







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.