This looks like the exact thing that I need for my project, however I'm at a loss how to use it. Your documentation is pretty sparse. Can you give me an example code snippet?
- I need to monitor INSERTs and UPDATEs and DELETEs to table JET_WB_ITM
- I need to monitor INSERTs and UPDATEs and DELETEs to table JET_GPS_CLN
- If possible, I'd like to NOT monitor the above, when the event was initiated by the user who made the INSERT, UPDATE or DELETE. IOW, the user who made the event happen, doesn't need to be notified that the event happened, because they already know that.
I have put an IBCAlerter component on my Data Module and the connection is set to my IBCConnection. But that's as far as I dare go, until I find out the proper way to activate it and enter the events.
- Does it hurt if I set AutoRegister to True at design time? (Why is it defaulted to False)?
- Does it hurt if I set Active to True at design time?
- Why is there an "AutoCommit"? I'm not committing anything with this component, I'm just wanting to "watch" for something.
- Exactly what is the syntax for making at event to "alert" on?
Thanks.
TIBCAlerter: First time using it... How do I use it?
-
RedOctober2013
- Posts: 9
- Joined: Thu 02 May 2013 22:52
Re: TIBCAlerter: First time using it... How do I use it?
IBDAC includes a demo with a sample of using the TICAlerter component.
Description of properties, methods and events of the TICAlerter component is provided in our documentation
http://www.devart.com/ibdac/docs/index. ... embers.htm
Setting the AutoRegister and Active properties to True at design time won't lead to retrieving of the events at design time. Events retrieving is available only at run time.
If you won't to distinguish actions performed by different users, you can add user name to the on-event message, for example:
More details about events can be found in the Firebird documentation.
Description of properties, methods and events of the TICAlerter component is provided in our documentation
http://www.devart.com/ibdac/docs/index. ... embers.htm
Setting the AutoRegister and Active properties to True at design time won't lead to retrieving of the events at design time. Events retrieving is available only at run time.
If you won't to distinguish actions performed by different users, you can add user name to the on-event message, for example:
Code: Select all
POST_EVENT(current_user ||': INS_TAB1').