George,
I have more insight on the occurance of error 2005, at least in this instance. The client had just run a conversion from our DOS app and there was a primary key violation so the primary key on 1 table was not created. This kept a relationship in the dataenvironment from loading and generated the error. I wish the error message were a little more informative. The record number referred to in the message is the actual record number in the DBC file.