Is it really true that there is just the SQL help but absolutely no gui help for EDB manager? I struggle with it quite a bit.

For instance, how do I enforce FK constraint of the kind

countryid in table addresses must exist in table countries ?

Thanks in advance for any pointers
Darrell

Darrell,

* Alter the table ADDRESSES
* Click on the Constraints tab
* Add the Constraint name
* Select Foreign key from the Type drop down list
* Select the Columns tab and select the CountryID from the table Columns list
* Select the Parameter tab and Select COUNTRIES as the Target Table, for the target
constraint select the Primary Key of the COUNTRIES table (presumably the primary key has
been defined using an ID column), then select the actions you require.

You should then be done . . .

Richard Harding

Darrell,

<< Is it really true that there is just the SQL help but absolutely no gui
help for EDB manager? I struggle with it quite a bit. >>

The GUI help is coming, and was delayed because we had to re-do the way it
works due to Vista and issues with WinHelp.   It should be available around
the time 2.03 is released.  It wasn't originally included with the EDB
Manager due to the fact that it was in a major state of flux for the first
year.  It will be finally fairly stable in terms of features as of 2.03.

--
Tim Young
Elevate Software
www.elevatesoft.com

Richard:

that's how I figured it should work. I select the Country table as target but the target constraint dropdown remains empty...

I have an index on an id field in the country table - though I cannot see anywhere where you'd make a distinction between regular and primary
indices in EDB manager (like I could in DBIsam's manager).

Any suggestions?

TIA,
Darrell

Darrel,

<< that's how I figured it should work. I select the Country table as
target but the target constraint dropdown remains empty...
I have an index on an id field in the country table >>

Indexes don't matter - you must have at least a "Primary Key" or
"Unique" constraint defined on the table in order to be able to use it
as a target table.

<< though I cannot see anywhere where you'd make a distinction between
regular and primary indices in EDB manager (like I could in DBIsam's
manager).>>

In terms of RI, you do not deal with indexes but with "constraints".
The concepts of primary or regular indexes doesn't exist anymore in EDB
- all indexes are equal except for the fact that some of them are
automatically created by EDB when you define "Primary Key" or "Unique"
constraints on tables.


--
Fernando Dias
[Team Elevate]