Hi Juan, Well I'll be.
It doesn't seem to have anything to do with the order of the date, it just when you have the letter formatted date fields eg DDD/MM/YYYY or DMM/DD/YYYY then the Shift-F9 Import Transaction Log does not correctly import the Date field. Fortunately, the Export T-Log is created exactly the same as when you use DDD/MM/YYYY or DDMY99/99/9999, so fortunately if you notice the problem you can change the data field from DDD/MM/YYYY to DDMY99/99/9999 and the import works fine again. Everything seems fine for the Shift-F7 Built in Short Reports export and CTRL-F5 import of WP format files, whichever date format you use. I have never used the DDD/MM/YYYY format, they introduced it after I had already gotten used to the DDMY99/99/9999 and fortuitously in this case it is hard to teach old dogs new tricks; fortuitously because these days I only generally interact with DP applications via T-Logs for web apps. Thanks for bringing this to everyone's attention Brian -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Juan A. Salhus R. Sent: Tuesday, 17 February 2009 2:44 AM To: Dataperfect Users Discussion Group Subject: [Dataperf] Bug in Export Import LOG In Chile, (SudAmerica) we use the data field like DDMMYYYY. When i define a field as DD/MM/YYYY in a panel they work fine but when i export the data to a LOG for a big Clean the problem apears The process o export work but when i import the data the error is generated at the date field they no recognice the format DD/MM/YYYY. The solution is change all date field as ddmyy99/99/9999 but there many applications generated by this way regards Juan A. Salhus _______________________________________________ Dataperf mailing list [email protected] http://lists.dataperfect.nl/mailman/listinfo/dataperf _______________________________________________ Dataperf mailing list [email protected] http://lists.dataperfect.nl/mailman/listinfo/dataperf
