 | |
#231
 
| |||
| |||
|
Re: Help with Paradox 9 table schema -
08-21-2008
, 10:38 AM
|
OK, so after playing around with ObjectPAL for about an hour, could someone show me how to create a cascading referential integrity link on a field TransactionID in a parent table called Transactions and a child table called TransactionDetails? In one of those articles on www.thedbcommunity.com called "Do It Yourself Referential Integrity", the author declines to show a working code sample because it is unreliable. Well, I'd still like to know how. I don't care if it's unreliable. |
If you have ObjectPAL, then we assume you have access to a full copy of
Paradox. You're better off interactively restructuring a table in Paradox
than trying to do it in code. Even in non-Paradox environments, it is
unusual to have application code run DDL, and for what you described
earlier, you are only modiying two tables.
If you are trying to code for a release package, this is typically
accomplished in Paradox through code that renames table1, puts the new
structure of table1 in place by copying an empty table to it, then adding
the existing data back from the renamed original table. You'll need to
manage the RI widows and orphans during this process as well.
As far as working code for RI, again, if you have Paradox, the on-line help
may have an example.
--
Larry DiGiovanni
#232
| |||
| |||
|
|
OK, so after playing around with ObjectPAL for about an hour, could someone show me how to create a cascading referential integrity link on a field TransactionID in a parent table called Transactions and a child table called TransactionDetails? In one of those articles on www.thedbcommunity.com called "Do It Yourself Referential Integrity", the author declines to show a working code sample because it is unreliable. Well, I'd still like to know how. I don't care if it's unreliable. |
If you have ObjectPAL, then we assume you have access to a full copy of
Paradox. You're better off interactively restructuring a table in Paradox
than trying to do it in code. Even in non-Paradox environments, it is
unusual to have application code run DDL, and for what you described
earlier, you are only modiying two tables.
If you are trying to code for a release package, this is typically
accomplished in Paradox through code that renames table1, puts the new
structure of table1 in place by copying an empty table to it, then adding
the existing data back from the renamed original table. You'll need to
manage the RI widows and orphans during this process as well.
As far as working code for RI, again, if you have Paradox, the on-line help
may have an example.
--
Larry DiGiovanni
 |
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.