> hi all--
>
> I'm not sure if this should be in this group or not, but, i'll take a
> shot.
>
> i'm using FB 2.1, IBO 4.8.7 and D6
>
> it's tough to put a finger on the "problem" because it's not a constant
> issue. on my computer when i run the application against the DB's i've
> received from my customers, I never see the problem.
>
> they do not see it everytime they execute the exact same sequence of
> steps in the application either, so, I think that removes the odds of
> it being a source code level bug.
>
> here's what it seems like it is: something to do with the speed /
> sequencing of my application, Firebird and the database.
>
> what is it: random errors returned and they are usually Access
> Violation errors OR "dynamic SQL error -206 unknown column".
>
> the column named in the error is never a column in the table (for
> example "K-000") AND my SQL to fetch the query is always "select * from
> atable". the source level query is persistent and has all the fields
> in it at the source code level (ie. they're created in source and in
> the query ie. persistent).
>
> the customers that see this error all have the same install setup:
>
> a server that has a single install of my application that also has the
> database & firebird on it. remote PCs on the LAN execute / share that
> single EXE on the server across the LAN on their PCs.
>
> they will be running fine, then do the exact same thing and it AV
> Errors or returns the "-206 unknown column" error. then? it works fine
> again for a while.
>
> it's almost like FB, the database and my application are not
> syncronized for the result query. i know how odd that sounds.
>
> can anyone shed any light on this or suggest a better way to run the
> application so there is only a single EXE being shared?
>
> TIA
> kelly

sounds like 'your error' to me.
IBO wants to know the primary key. You are using select * and probably using
'keylinks auto define' and not declaring a specific key which forces IBO to
use the DBKEY to retrieve specific rows when it needs to refresh its query
buffer. Are these queries all from normal tables? This happens most from a
join. Anyway I think this is an IBO list issue. Swallow and report the
exception for the moment until you find out why, so your users aren't
annoyed by it.
Alan