![]() | ![]() Products ![]() ![]() ![]() ![]() |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread |
Messages 1 to 10 of 10 total |
![]() |
Mon, Sep 10 2012 12:49 PM | Permanent Link |
Petter Topp | Hi.
I'm using dbisam's export/import routines for moving some data from one computer to the other. When trying to import the csv file we get error 11309: --------------------------- Apro_avregning --------------------------- DBISAM Engine Error # 11309 An error occurred during the import into the table 'EUROP_AVR_TRANS' - Invalid expression 03:05:00.000 found in import data. --------------------------- OK --------------------------- The value 03:05:00.000 belongs to a TIME field. This value is the same as in the csv file, but in the table (Using Dbsys) the value is shown as 03:05:00 The csv file was generated on a Windows XP computer with language set to Norwegian. I don't believe this has anything to do with the OS version, since I have been able to reproduce this on my computer running Win 7. Strange thing is that I have recently tested that this worked without any problems.... Any Idaes on whats going on? Petter Topp Dbisam 4.30 |
Mon, Sep 10 2012 1:00 PM | Permanent Link |
Fernando Dias ![]() | Peter,
There is a Win 7 bug with regional settings that might be the cause of what you are experiencing. What happens is sometimes when you change regional settings, the system shows you one region but internally reports the previous one. A workaround is to change it again - change the regional settings to something else and then to the region you want again. -- Fernando Dias [Team Elevate] |
Mon, Sep 10 2012 1:04 PM | Permanent Link |
Petter Topp | Hi Fernando.
This raises a couple of questions though: 1. The machine producing the file was a Windows XP computer. 2. The value is still wrong, or? Petter "Fernando Dias" skrev i nyhetsmeldingen: 48BFD724-A682-455E-801C-FD569E3C58C7@news.elevatesoft.com ... Peter, There is a Win 7 bug with regional settings that might be the cause of what you are experiencing. What happens is sometimes when you change regional settings, the system shows you one region but internally reports the previous one. A workaround is to change it again - change the regional settings to something else and then to the region you want again. -- Fernando Dias [Team Elevate] |
Mon, Sep 10 2012 1:38 PM | Permanent Link |
Fernando Dias ![]() | Peter,
I don't know if the bug was present in Xp or not, but it doesnt really matter, what matters is if the settings used to import match the formats that were used to produce the file. In any case, I'm thinking of other possible causes... Please look into the exported file and tell me, is there a blank space between 03:05:00.000 and the ',' next to it? -- Fernando Dias [Team Elevate] |
Mon, Sep 10 2012 2:06 PM | Permanent Link |
Petter Topp | Fernando, you are right there are a blank before the following separator:
;"123";101694;;"K";183060;510;12.7;12.7;;1;1;;;;;;"021856";"H";;;;;"LAM O+ ORDINÆR";2012-09-06;03:05:00.000 ;;;;"2043 Petter "Fernando Dias" skrev i nyhetsmeldingen: E8C9E4D7-1CDB-4378-AB16-BB48BEF42EE6@news.elevatesoft.com ... Peter, I don't know if the bug was present in Xp or not, but it doesnt really matter, what matters is if the settings used to import match the formats that were used to produce the file. In any case, I'm thinking of other possible causes... Please look into the exported file and tell me, is there a blank space between 03:05:00.000 and the ',' next to it? -- Fernando Dias [Team Elevate] |
Mon, Sep 10 2012 2:18 PM | Permanent Link |
Fernando Dias ![]() | Peter,
Can you export the file again? I suspect it has been exported using am/pm format, that's what I think is adding the extra space. If not, can you do a test with a couple of rows only, removing the extra space and importing without the ampm specifier in the format ? -- Fernando Dias [Team Elevate] |
Mon, Sep 10 2012 3:07 PM | Permanent Link |
Petter Topp | Fernando, I'm performing the export/import in my application...
I have however performed the export using dbsys, and removing the .zzz ampm specifier. Using Dbsys to import into the other database now works given that I have similar settings for the time format... So, I have a fix - don't use the ampm specifier when using import/export..... OR? This is my code: tblAvrTransFilter.ImportTable(OpenDialog1.FileName, Chr(Byte(';')), False, Nil); tblAvrTransFilter.ExportTable(SaveDialogVarmvekt.FileName, Chr(Byte(';')), False, Nil); As you can see the formats are not specified at all, so I guess that default settings are used. Petter "Fernando Dias" skrev i nyhetsmeldingen: 7A9BD7F5-8D68-4237-A4CF-D1340D13A1F7@news.elevatesoft.com ... Peter, Can you export the file again? I suspect it has been exported using am/pm format, that's what I think is adding the extra space. If not, can you do a test with a couple of rows only, removing the extra space and importing without the ampm specifier in the format ? -- Fernando Dias [Team Elevate] |
Mon, Sep 10 2012 5:52 PM | Permanent Link |
Fernando Dias ![]() | Peter,
<< So, I have a fix - don't use the ampm specifier when using import/export..... OR?>> Yes, thats what I was thinking, that exporting and importing without the ampm specifier would work. There is perhaps a bug in the export when using ampm specifier with some Regional Settings but I'll have to confirm that. Meanwhile, I think it works well if you don't use ampm. -- Fernando Dias [Team Elevate] |
Tue, Sep 11 2012 1:48 PM | Permanent Link |
Fernando Dias ![]() | Peter,
In fact it's not exactly a DBISAM bug. It's the FormatDateTime Delphi function (used in EXPORT) that incorrectly adds an extra space at the end when a format like 'hh:mm:ss.zzz ampm' is used with Regional Settings that don't use AM/PM. The workaround is to use 'hh:mm:ss.zzz' format to export and import. -- Fernando Dias [Team Elevate] |
Mon, Oct 1 2012 10:39 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. ![]() | Fernando,
<< In fact it's not exactly a DBISAM bug. It's the FormatDateTime Delphi function (used in EXPORT) that incorrectly adds an extra space at the end when a format like 'hh:mm:ss.zzz ampm' is used with Regional Settings that don't use AM/PM. The workaround is to use 'hh:mm:ss.zzz' format to export and import. >> This is fixed in 4.34, which should be out soon. Thanks, Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Wednesday, August 14, 2024 at 03:12 PM | Privacy Policy![]() © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? ![]() |