|
Yes Evan, once the date has been input in a date field, it will take
internally the YYYYMMDD format and will be stored as such. Even if you MI will
let you input the date in the format set in the Control Panel and will display
it in the browser. My MI accepts only ddmmyyyy dates but will convert them in
its own format. Then at export time, you have well described what happens. I guess that if you want to see your own format in the exported text,
you will need another column (string that one) that you would update with
formatdate$() of the date column just before exportation. But you will have
both column in the txt file. Jacques PARIS e-mail (>>>19.12.00) [EMAIL PROTECTED] For
MapInfo support, see the Paris PC Consult enr. site at http://www.total.net/~rparis/gisproducts.htm For
MapBasic questions see the J.Paris site at http://www.total.net/~jakesp/index.htm -----Original
Message----- Jaques,
When I fill the Effective Date Field using Update Column, I enter it as
"MM/DD/YYYY" and when I click on the objects in my map with the info
tool, they are displayed as "MM/DD/YYYY". However, when I export
the table to a text file and I open up the test file with Notepad, the dates in
the text file were exported as YYYYMMDD. I don't ever use the curdate()
or FormatDate$(curdate()) functions. If I go into Table Maintenance, that
Effective Date field is set to "date". So, you're saying that starting
with MI-pro v4.5 all dates in a date field will be exported as a String looking
like: YYYYMMDD? -Evan
MacDougall ([EMAIL PROTECTED]) GIS
Specialist ACE USA Flood
Services -----Original Message----- It is no a bug. MapBasic help states clearly that
curdate() is always in YYYYMMDD, but it was not always the case and you are
right to “register” the change. If you want to have the date in the format that is
defined in Control Pannel, then you must use FormatDate$(curdate()) The change in the curdate() output format took place
with version 4.5, that saw also the addition of the formatdate$() function to
have more flexibility in the date format. But you must be aware that the output
of formatdate$() is a STRING, not a DATE field anymore. Jacques Jacques PARIS e-mail (>>>19.12.00)
[EMAIL PROTECTED] For MapInfo support, see the Paris PC
Consult enr. site at
http://www.total.net/~rparis/gisproducts.htm For MapBasic questions see the J.Paris site
at
http://www.total.net/~jakesp/index.htm -----Original
Message----- Hello All,
I have some tables that I am exporting to text
files. One of the fields in my tables is the Effective Date which is
type: "Date". I used to use MI-Pro v4.1.2. When I
exported my tables to text files, the date was displayed in the text file like
this: 01/10/2001
(MM/DD/YYYY) However, now I am using
MI-Pro v.6 and the date in the text file is now being displayed like
this: 20010110
(YYYYMMDD) I have been reading
through the manual and fiddling with MapInfo, but I can't find any kind of
preference or option or setting that will change the way the date is
exported. Is this a bug, or is this some kind of weird new date exporting
standard? I just tested it this
morning using different dates from 1998 thru 2001. MI-Pro v.4.1.2
exported all dates to the correct setting of MM/DD/YYYY. MI-Pro v.6
exported all dates to the weird setting of YYYYDDMM with no "/"'s for
all years including 1998 & 1999. (both programs are on different
computers, btw) What's going on?! -Evan MacDougall
([EMAIL PROTECTED]) |
Title: MI-L Possible bug in Date Export
- MI-L Possible bug in Date Export Macdougall, Evan 1065
- RE: MI-L Possible bug in Date Export Jacques Paris
- RE: MI-L Possible bug in Date Export Macdougall, Evan 1065
- Jacques Paris
