Are SQL constrains observed by the Pervasive Btrieve engine as well?
Referential Integrity constraints are always enforced, because this functionality is implemented by the MicroKernel. So, no matter what interface is used by the application, the constraints are enforced. This is not true of triggersthe SQL engine enforces and calls the triggers as a result of insert/update/delete operations made by an SQL application. Since the MKDE does not currently support triggers, direct Btrieve (non-SQL) write operations are disallowed if triggers are defined on a particular table. In other words, Btrieve write access is not available for files with defined triggers.
