1. Dont change the key. Use a surrogate? I'd say its more a design issue
- the end user should never really know the ID!!!
2. COPY the records - make a NEW master, then new detail, then remove
the detail and remove the master - the only way, I think. Paradox is
fairly insecure IIRC with referential integrity, tho.
N
Mark Derricutt wrote:
>
> On Mon, 6 Sep 1999, Aaron Scott-Boddendijk wrote:
>
> > And furthurmore it wouldn't make sense to in this case where there is
> > no stated relationship between the tables... I thought I saw somewhere
> > that ORACLE8 (or was it 8i) supported updatable views which can be joins
>
> Well the situation I have, is I have a master/detail table arangement, and
> I have a requirement to be able to "rename" an object in the master table,
> which is, change its key field, and I was wanting to have one query which
> would update the master table, -and- the child table.
>
> This is against a paradox tables (at the mo).
>
> --
> Mark Derricutt | Chalice of Blood
> Software Developer | New Zealand Christian Music News
> Auckland, New Zealand | http://www.chalice.gen.nz
> [EMAIL PROTECTED] | UIN: 1934853
>
> Getting jiggy with Gamma Ray - The Guardians Of Mankind
>
> ---------------------------------------------------------------------------
> New Zealand Delphi Users group - Database List - [EMAIL PROTECTED]
> Website: http://www.delphi.org.nz
--
Nic Wise - +64.21.676.418 - +64.9.277.5309 - [EMAIL PROTECTED]
---------------------------------------------------------------------------
New Zealand Delphi Users group - Database List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
