Gary Kjos
garykjos at gmail.com
Sun Oct 16 22:34:35 CDT 2011
Whew! I've had that same issue with Oracle ODBC data when I didn't specify the key's correctly when the link process didn't see them automatically. Glad you solved the mystery Brad. And thanks for letting us know. GK On Sun, Oct 16, 2011 at 9:12 PM, Brad Marks <BradM at blackforestltd.com> wrote: > Oh Boy... Do I ever feel STUPID! > > Because of the suggestion, to Relink the Firebird table in question, I > decided to do so. > > In the process of doing the Relink, Access displayed a message "To > ensure data integrity and to update records, you must choose a field or > fields that uniquely identify each record". > > As I understand it, the field(s) selected results in establishing the > Primary Key on the Access side for the linked table. > > When doing the Relink, it dawned on me that I had earlier selected the > wrong field to uniquely identify each record. I believe that this > mistake resulted in the strange results that I was seeing. > > This mistake was mine. For a time, I thought that I had stumbled on > some sort of bug, or angered the "ODBC gods" :-) > > > Thanks again for the help. Once again, the advice given by others here > in the AccessD forum has helped to resolve a problem (and keep me from > pulling out even more of my hair). > > I really appreciate the help and advice that is provided on this forum. > > Sincerely, > > Brad > -- Gary Kjos garykjos at gmail.com