At 26/02/2002 10:59 PM, you wrote:

>To the forum:
>
>I have other tables that deal with the details of the analysis of
>these units. They each have a foriegn key that links back to the
>primary key of the main table mentioned in previous paragraph. For
>instance, if my given unit has to have four parts replaced, I have a
>table for replaced parts and supplier info that has the foreign key
>to tell me which serial number unit the parts were replaced on.
>
>I tried to use Access to set up a form and subform, but apparently
>the foreign key relationships that I set up using IB Expert to
>configure the Interbase database are not recognized by Access. It
>doesn't make a whole lot of sense to declare these relationships in
>both Access and Interbase. Has anyone dealt with this type of
>problem successfully? Is anyone out there familiar with using the
>Easysoft driver with Access to get desired results?

You will have to setup the relations again in Access, because foreign keys
are more of a set of rules applied to the tables to enforce data integrity
for your database. It's not the master-detail relationships for
navigation. Access knows how to talk to Access DB, but doesn't really know
much of other DB's and you have to setup those relationships. Even in
Delphi, the developer has to setup the master-detail relationship for the
tables and queries, even though there are foreign keys defined.

The foreign keys defined at the database level helps to ensure that your
data is the way you want it, especially if someone is trying to modify it
from outside your application.


Daniel Rail