Subject RE: [firebird-support] Composite vs single column keys
Author Svein Erling Tysvær
>This is not so easy to emulate with a SELECT statement. I have come up with this:
> WHERE Company > :Company OR
> (Company = :Company AND Account > :Account) OR
> (Company = :Company AND Account = :Account AND Division > :Division) OR

I think

WHERE Company >= :Company
AND (Company > :Company
OR (Account >= :Account
AND (Account > :Account
OR (Division >= :Division
AND (Division > :Division
OR (Department >= :Department
AND (Department > :Department
OR (EffectiveDate >= :EffectiveDate
AND (EffectiveDate > :EffectiveDate
OR ControlNumber >= : ControlNumber)))))))))

will achieve the same thing with lesser code.

Regarding the programmers opposing changing to a database, I would actually suggest that you implement something like they want. However, I would also recommend you to tell them it is like trying to make a sports car behave like a train and ask them if you could be allowed to change one (smallish, but sluggish) program so that it utilized Firebird the way it was intended to (and then let them compare the two versions).