> would not having KeyLinks defined (all i have is a primary key defined
> in the tables) cause the problem on only some computers?
>
> the troubling issue is, if i run my application on my PC with my
> customer's database, i do not get any error messages. i've never seen
> the errors I'm talking about on my local install with a local database
> (ie. running it all on my C:). it's only on server installs of the
> executable and users running the app across a LAN that the errors have
> ever occured (when they do).
>
> if they run it on theirs, they get the messages one time in 10
> executions of the exact same function with the exact same SQL with the
> exact same record set being returned.
>
> it's that inability of the problem to be repeatable that has me stumped
> and thinking it's not in my source code directly like a "syntax error"
> or a simple logic error.
>
> thanks!
> kelly

AFAIAA, The nature of using/relying on DBKEYs is that they are not reliable
across transaction boundaries. In a multi user environment in a multi
generational database, the DBKEYs change - Unique keys are constant (unless
you have a weird habit of changing them).
So if other people are relying on there DBKEY to locate a record which you
have just committed, their DBKEY is no longer valid. That's why thre is a
sense of unreliability about your issue.

read this
http://www.cvalde.net/document/mysteriousDbKeyII.htm

Alan