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

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

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

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

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

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

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
>

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.