> >German, you say "not unique" for the FKs. Exactly how "not unique" is
> >this? It is OK to have a foreign key to customer in the order table,
> >but it is not OK to have a foreign key to status when 90% of the
> >records have the status 'Completed'.
> >
> I font have that kind of foreign key (like status) but yes can happen
> there the same key in the 90% of records.
> Thats is bad? So please explain me how can i manage that in a real life
> app. If that key is by example payment, how can i know if the people
> will pay with cash or visa before create the table?
> I really dont understand why that is a trouble in firebird.Must be
> another solution. I dont want to remove foreign keys and lost
> referential integrity.

You shouldn't. This is an implementation problem. The implementation
should be improved.

With regards,

Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL
Server.
Upscene Productions
http://www.upscene.com