Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 1 to 5 of 5 total |
v1 import problems |
Mon, Aug 24 2009 5:32 PM | Permanent Link |
Michael Fullerton | I am having some major problems importing CSV records in v1.09. I have
a single record file. If I try to import it says the first timestamp field can't be null. But its not null. I think its perhaps due to the empty line at the end of the file so I remove that. Now it says the file is truncated or corrupt. Attempting to import from EDBMgr it says the first date field can't be null. Record is below. Looks like I reported this problem in 1.06 and it was supposed to be fixed in 1.07. "1","8/24/2009","8/24/2009 8:00","8/24/2009 10:30","218","ACCT T","Unger Larry S","w1'-20","ad",,,"12/14/2009",,,,,,True The first col is a generated integer. |
Tue, Aug 25 2009 8:18 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Michael,
<< I am having some major problems importing CSV records in v1.09. I have a single record file. If I try to import it says the first timestamp field can't be null. But its not null. I think its perhaps due to the empty line at the end of the file so I remove that. Now it says the file is truncated or corrupt. Attempting to import from EDBMgr it says the first date field can't be null. Record is below. Looks like I reported this problem in 1.06 and it was supposed to be fixed in 1.07. >> We don't have any other reports of import issues other than that last one for 1.07 that was fixed: http://www.elevatesoft.com/incident?action=viewrep&category=edb&release=1.06&type=f&incident=2481 I'm assuming that you're not using the Unicode version of EDB ? If you want to send me the database catalog, I can try the import here for you. -- Tim Young Elevate Software www.elevatesoft.com |
Tue, Aug 25 2009 4:43 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Michael,
Following up on this (thanks for the files). What is the actual IMPORT TABLE statement that you're using ? It appears that you're not using the proper date format for the import (mm/dd/yyyy). If the date format isn't correct, then the column isn't populated. However, I'll see about getting this changed so that it issues a proper import error instead. -- Tim Young Elevate Software www.elevatesoft.com |
Thu, Aug 27 2009 6:57 PM | Permanent Link |
Michael Fullerton | On Tue, 25 Aug 2009 16:43:58 -0400, "Tim Young [Elevate Software]"
<timyoung@elevatesoft.com> wrote: >Michael, > >Following up on this (thanks for the files). What is the actual IMPORT >TABLE statement that you're using ? It appears that you're not using the >proper date format for the import (mm/dd/yyyy). If the date format isn't >correct, then the column isn't populated. However, I'll see about getting >this changed so that it issues a proper import error instead. I had m/d/yyyy date format and that was not the problem. The problem was the time format of h:m. I changed to hh:mm and it worked. But h:mm should work too. |
Mon, Aug 31 2009 3:19 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Michael,
<< I had m/d/yyyy date format and that was not the problem. The problem was the time format of h:m. I changed to hh:mm and it worked. But h:mm should work too. >> Okay, yes you're correct. EDB is not handling the hours portion properly if the format contains just 'h' and not 'hh'. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Thursday, May 23, 2024 at 03:39 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |