Re: Data Export:: Date Problem, posted by Stefan Ritt on Mon Feb 11 22:24:37 2008
|
| Richard Ecclestone wrote: |
|
Hi
Im currently experimenting with Elog to see if we can use it to track maintenance work. But Ive come up against a problem, When I export the data to a csv file,
the date has a comma inserted between the day of the week and the rest of the date. This means that all the fields are then shifted to the right after the date.
This looks like a bug to me, the test records included in the demo does not exhibit this problem, until a new record is added.
|
What about exporting record separated by a semicolong ";" ? |
|
Re: Data Export:: Date Problem, posted by Stefan Ritt on Mon Feb 11 22:33:37 2008
|
| Stefan Ritt wrote: |
|
| Richard Ecclestone wrote: |
|
Hi
Im currently experimenting with Elog to see if we can use it to track maintenance work. But Ive come up against a problem, When I export the data to a csv file,
the date has a comma inserted between the day of the week and the rest of the date. This means that all the fields are then shifted to the right after the date.
This looks like a bug to me, the test records included in the demo does not exhibit this problem, until a new record is added.
|
What about exporting record separated by a semicolong ";" ?
|
I fixed that in SVN revision #2040, the comma is simply replaced by a space in the date string. |
|
Re: Data Export:: Date Problem, posted by Richard Ecclestone on Tue Feb 12 08:54:48 2008
|
| Stefan Ritt wrote: |
|
| Stefan Ritt wrote: |
|
| Richard Ecclestone wrote: |
|
Hi
Im currently experimenting with Elog to see if we can use it to track maintenance work. But Ive come up against a problem, When I export the data to a csv file,
the date has a comma inserted between the day of the week and the rest of the date. This means that all the fields are then shifted to the right after the date.
This looks like a bug to me, the test records included in the demo does not exhibit this problem, until a new record is added.
|
What about exporting record separated by a semicolong ";" ?
|
I fixed that in SVN revision #2040, the comma is simply replaced by a space in the date string.
|
Hi Stefan
Thanks for the quick reply.
We seem to be running 2012 - Which may explain the problem - I will see with our system administrator why we are not running 2040. By the way I also had this problem when running the windows version.
Cheers.. Richard |
|
Re: Data Export:: Date Problem, posted by Richard Ecclestone on Tue Feb 12 10:52:17 2008
|
| Richard Ecclestone wrote: |
|
| Stefan Ritt wrote: |
|
| Stefan Ritt wrote: |
|
| Richard Ecclestone wrote: |
|
Hi
Im currently experimenting with Elog to see if we can use it to track maintenance work. But Ive come up against a problem, When I export the data to a csv file,
the date has a comma inserted between the day of the week and the rest of the date. This means that all the fields are then shifted to the right after the date.
This looks like a bug to me, the test records included in the demo does not exhibit this problem, until a new record is added.
|
What about exporting record separated by a semicolong ";" ?
|
I fixed that in SVN revision #2040, the comma is simply replaced by a space in the date string.
|
Hi Stefan
Thanks for the quick reply.
We seem to be running 2012 - Which may explain the problem - I will see with our system administrator why we are not running 2040. By the way I also had this problem when running the windows version.
Cheers.. Richard
|
Hi Stefan
Our IT administrator has just downloaded and installed the latest source code from the site and installed it. We still now have version 2012?
Where do we get version 2041 ?
Cheers, Richard
|
|
Re: Data Export:: Date Problem, posted by Stefan Ritt on Tue Feb 12 11:42:01 2008
|
| Richard Ecclestone wrote: |
|
Our IT administrator has just downloaded and installed the latest source code from the site and installed it. We still now have version 2012?
Where do we get version 2041 ?
|
The bleeding edge version you get always from our SVN server, but you have to recompile it yourself. For your convenience, I just made you a version 2.7.2-3 containing the latest source code. |
|
Re: Data Export:: Date Problem, posted by Richard Ecclestone on Tue Feb 12 20:40:53 2008
|
| Stefan Ritt wrote: |
|
| Richard Ecclestone wrote: |
|
Our IT administrator has just downloaded and installed the latest source code from the site and installed it. We still now have version 2012?
Where do we get version 2041 ?
|
The bleeding edge version you get always from our SVN server, but you have to recompile it yourself. For your convenience, I just made you a version 2.7.2-3 containing the latest source code.
|
Thanks Stefan
Everything works now. |
Converting dates from an Excel import into ELOG, posted by Fergus Lynch on Thu Jan 24 13:50:10 2008
|
Hi,
I'm importing an Excel spreadsheet into ELOG through CSV format. All working fine apart from dates.
Dates are exporting from Excel in the format "day/month/year" so 1st January 2008 is exported as 01/01/2008 in the CSV.
However all dates are displayed in ELOG as "01/01/1970" regardless of the field content, and looking at the raw ELOG data file dates are displayed as numeric's - so for example 01/01/2008 is "1199188800"
Can you tell me how dates are computed/stored in ELOG so that I can do the necessary conversion.
Many Thanks
Fergus |
|
Re: Converting dates from an Excel import into ELOG, posted by Fergus Lynch on Thu Jan 24 16:50:16 2008
|
| Fergus Lynch wrote: |
|
Hi,
I'm importing an Excel spreadsheet into ELOG through CSV format. All working fine apart from dates.
Dates are exporting from Excel in the format "day/month/year" so 1st January 2008 is exported as 01/01/2008 in the CSV.
However all dates are displayed in ELOG as "01/01/1970" regardless of the field content, and looking at the raw ELOG data file dates are displayed as numeric's - so for example 01/01/2008 is "1199188800"
Can you tell me how dates are computed/stored in ELOG so that I can do the necessary conversion.
Many Thanks
Fergus
|
S'ok - looked up the documentation  and have converted Excel dates to ELOG 'seconds since 01/01/1970' and all has come over fine!
Thanks
Fergus |