Page 1 of 1

[Closed] Bug in TRIGGER

PostPosted: Wed Mar 29, 2017 1:42 am
by dreamquartz
Hi All,

As mentioned in the following topic:, I must conclude that there is indeed a bug in the TRIGGER process.
The moment a DataBAse is opened, does NOT mean that the TRIGGER is active.
I need to enter a wrong (=existing) CertificateCode first, before the TRIGGER is active. This does not make sense.
Is it not so that the "database.script" is read in its entirety, to build the database structure?

Hope someone can shed some light on this,


Re: Bug in TRIGGER

PostPosted: Wed Mar 29, 2017 2:05 am
by dreamquartz

There is definitely more going on.
When closing and opening the database again, the TRIGGER is not active.

This might be caused by either the TRIGGER is incorrect, or it is a BUG.
I will consider it as the TRIGGER being incorrect for now, so I close this topic. and will re-open the above mentioned one.