Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread |
Messages 1 to 8 of 8 total |
error 11309 |
Tue, Oct 9 2007 1:02 PM | Permanent Link |
"AlanL" | Hello,
I am getting this error message:- "DBSIAM Engine Error # 11309 An error occurred during the import into the table 'PURCH' - Missing in import data." I don't know what error 11309 means. I don't see references to this in the manual, Appendix- error codes. I am using DBisam4 4.25 build 6 many thanks, AlanL |
Tue, Oct 9 2007 3:50 PM | Permanent Link |
Eryk Bottomley | AlanL
> I am getting this error message:- > "DBSIAM Engine Error # 11309 An error occurred during the import into the > table 'PURCH' - Missing in import data." > > I don't know what error 11309 means. I don't see references to this in the > manual, Appendix- error codes. > I am using DBisam4 4.25 build 6 That error code resolves as DBISAM_IMPORTERROR which is a generic error meaning that the import parser doesn't like something about the formatting of the import source file. Eryk |
Tue, Oct 9 2007 10:22 PM | Permanent Link |
"AlanL" | Thank you Eryk, I will check the import files for errors
regards, AlanL "Eryk Bottomley" <no@way.com> wrote in message news:130D2908-A3F1-4025-8644-463005D73838@news.elevatesoft.com... > AlanL > > >> I am getting this error message:- >> "DBSIAM Engine Error # 11309 An error occurred during the import into the >> table 'PURCH' - Missing in import data." >> >> I don't know what error 11309 means. I don't see references to this in >> the manual, Appendix- error codes. >> I am using DBisam4 4.25 build 6 > > > That error code resolves as DBISAM_IMPORTERROR which is a generic error > meaning that the import parser doesn't like something about the formatting > of the import source file. > > Eryk |
Wed, Oct 10 2007 12:06 AM | Permanent Link |
Phil Read | Just curious...
Is this ERROR related to your previous problem with the same error back in 2004 (so the page says) http://www.elevatesoft.com/scripts/incident.dll?action=viewrep&category=dbisam&release=4.11&type=f&incident=1852 |
Fri, Oct 12 2007 8:42 AM | Permanent Link |
"AlanL" | Hello Phil,
No, this is a different situation. the csv file is intact, imports into my table without error. Customer's data files are not corrupt. In a workgroup network setup it imports correctly. All Pc's were moved from a Workgroup to a Windows domain and that is when the "DBSIAM Engine Error # 11309" started. regards, AlanL "Phil Read" <phil@vizualweb.com> wrote in message news:46A88977-62CD-4656-9366-11383AEDF7A3@news.elevatesoft.com... > Just curious... > > Is this ERROR related to your previous problem with the same error back in > 2004 (so the page says) > http://www.elevatesoft.com/scripts/incident.dll?action=viewrep&category=dbisam&release=4.11&type=f&incident=1852 |
Fri, Oct 12 2007 6:27 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Alan,
<< No, this is a different situation. the csv file is intact, imports into my table without error. Customer's data files are not corrupt. In a workgroup network setup it imports correctly. All Pc's were moved from a Workgroup to a Windows domain and that is when the "DBSIAM Engine Error # 11309" started. >> Is it possible that during the move a path setting has changed such that you're importing a different file than what you might think ? -- Tim Young Elevate Software www.elevatesoft.com |
Thu, Oct 18 2007 2:43 PM | Permanent Link |
"AlanL" | Hello Tim,
sorry for delay. Yes it's possible, but I have to visit the site to confirm this myself and to see what else might be going on over there. I will let you know my findings. regards, Alan "Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message news:EC425B17-81CE-41C6-89F5-24E8B7AD2783@news.elevatesoft.com... > Alan, > > << No, this is a different situation. the csv file is intact, imports into > my table without error. > Customer's data files are not corrupt. > In a workgroup network setup it imports correctly. > All Pc's were moved from a Workgroup to a Windows domain and that is when > the "DBSIAM Engine Error # 11309" started. >> > > Is it possible that during the move a path setting has changed such that > you're importing a different file than what you might think ? > > -- > Tim Young > Elevate Software > www.elevatesoft.com > |
Mon, Dec 23 2013 10:16 AM | Permanent Link |
Chris Thornton | Just adding another possible cause....
I had this when importing a .CSV that had unix-style line endings. It had only LF when DBISAM expected CRLF. I had generated the .csv with a series of unix-like command-line utilities, and did not realize that I had messed this up (Notepad++ shows it nicely either way!). Just adding here, in case it helps someone out. |
This web page was last updated on Tuesday, September 17, 2024 at 04:19 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |