Migration might be too strong a term - I don't want my Firebird database to
bear too much resemblance to an old Paradox database. The database might serve
similar logical purposes, though. The domain advice is good in general -
char(16) character set octets, for example, would probably be a go
The case-insensitive collation option sounds the most seemless. I might have
to choose character sets more carefully - the DB I tested with was ISO8859_1
for a default, and I couldn't find a CI collation for it (maybe I needed to
look harder). The second is basically a simpler version of what
Sorry - it's been a long time since I last posted. My OP was verbose, lengthy
on preamble. I've gotten too accustomed to emailing users. Thanks.-MB
This was something I would resort to years ago in Paradox. Suppose I had a
table CORPORATION with columns S_KEY INTEGER, SUBSIDIARY_NAME CHAR(50) and a
table EMPLOYEE with columns CORPORATION_S_KEY INTEGER, NAME CHAR(50). S_KEY is
meant to be a surrogate key column with a PRIMARY KEY constrain
