Hi,

I am new to this forums and hope that someone might have come across this scenario:
1. I have to capture some TRIGGER events from one of the table in the sql server 2000. I have an active VB program that open a Serial Port (say COM 1).
2. I have no issue when data arrive at the port (event triggered captured).
3. However, when data arrived in SQL server table, I have no mean of getting the VB program to react based on the events. The VB supposed to get the data and process accordingly.
4. My question is: is there a way i can make the VB and sql Server to talk to each other based on events?

Thank you in advance.

I think you need to think about how VB and SQL interact. VB sends a request to SQL, SQL answers. On a trigger, it occurs just on SQL if there is not current VB connection or several VB connections how can SQL tell which VB session to do what. What you may want to do is have the SQL server put a file in a particual file path, then have the vb app check the existance of that file at an interval (say every minute). Thus the VB app can then do something that SQL tells it.

I think you also may get more help if you better explain what your trying to do....

This will be equivalent to polling the db or file. This is not what i wanted. I wanted an interrupt sort of events from the SQL.
It need not have to come from trigger but i only wanted to capture that trigger "event". The preferred mode is the vb subscribed to some SQL events and when the event are trigger, the vb programm will be notified.

What i am trying to achieve here is to get the vb to process some data from the db when certain data arrive at a particular table. The vb will always be live and not close down cos it is listening to oncomm from the USB port for incoming data.

Hope there is some advice regarding this issue.

If I understand what your trying to do I think you would have to have a vb app on the sql server. The sql event calls up the vb on the server and that vb app does something or calls some app on another computer. But for SQL to be the triggering event of a VB app I think your going to need to call up the VB on the SQL server from the command prompt useing something like the xp command shell functionality of SQL.