Subject | Re: [IBO] Re: Masterlinks demo - does not work ? |
---|---|
Author | wes@lexcraft.com |
Post date | 2000-12-28T21:05:40Z |
Joe,
the many advantages of client server databases is this sort of thing
can be done by the database SERVER, instead of by the client program.
In my documents for IB6, I find the relevant information/techniques in
the file DataDef.pdf under "Defining Integrity Constraints." (Pg 100).
What you'll want to do is, when defining your PayControlTable, specify
a foreign key that references the Employee table and for which you
specify ON DELETE CASCADE.
When an employee record is deleted, Interbase itself will then see to
it that the appropriate PayControlTable records get deleted, too.
-----------------------------
Wes Peterson
LexCraft Data Services
916.944.4870
http://www.lexcraft.com
wes@...
>Being new to Interbase and IBO, I may simply not understand but I canThat's the way it HAS to be done with many "desktop" databases. One of
>find no way to accomplish what I need.
>When I deleted the master (Employee) record, since the tables were
>linked master/detail, all I had to do was
>With PayControlTable Do
>Begin
> First;
> While Not Eof Do
> Delete;
>End;
>and all pay control records for the employee were deleted.
the many advantages of client server databases is this sort of thing
can be done by the database SERVER, instead of by the client program.
In my documents for IB6, I find the relevant information/techniques in
the file DataDef.pdf under "Defining Integrity Constraints." (Pg 100).
What you'll want to do is, when defining your PayControlTable, specify
a foreign key that references the Employee table and for which you
specify ON DELETE CASCADE.
When an employee record is deleted, Interbase itself will then see to
it that the appropriate PayControlTable records get deleted, too.
-----------------------------
Wes Peterson
LexCraft Data Services
916.944.4870
http://www.lexcraft.com
wes@...