Isn't this something that can be done with message queue or COM+ events? The ap can subscribe to message/event, and when there is a message, an event is published. The subscriber app responds to the event and displays the dispatch form or notice or whatever.

I thought the days of constantly polling for data/message were gone with COM+ events. Or, can you not use COM+ events in .Net? Is there an equivelent to COM+ events in .Net?

BOb


>I'm gonna mark your message as a favorite so that I can come back to it as I need to. <g>
>
>So, from what I understand, you need to regularly check whether a certain set of columns have certain values (running a SQL query). You currently do it in forms (with a timer, I'm guessing).
>
>I'd look at creating a thread for each check, with some kind of visual cue that lets the user know there's an issue, optionally calling up a form. IOW, if the operator is always in an "operator" form, having a place where it lists "unacknowledged dispatches" on the screen (hopefully always 0) that you can have the thread turn red with a click bringing up the detail form (or what's appropriate) may make sense. This way you can have the query be a SELECT COUNT() and just know there's an issue, with the form doing the full query (less network traffic also this way).
>
>To do this, set a thread to do the check and write back to the form as needed. I did a quick google search (www.google.com/microsoft does a great search of all MSFT related sites) and came back with these likely papers:
>
>http://abstractvb.com/code.asp?A=1020
>http://www.codeproject.com/vb/net/tracker.asp
>
>Hope this helps.
>
>yag
>
>
>>Please, thank everyone for their help!
>>Here is an intro:
>> The business has a client services operation in Bristol and a courier division in Kingsport. All calls are directed to client services. When a customer calls client services for a courier pickup, the operator needs to notify the dispatcher, who in turn, selects a courier and notifies them to make the pickup.
>>The problem is to automate the process so that the operator doesn't have to call the dispatcher and so the dispatcher doesn't have to call the courier.
>>
>>Here is the proposed solution:
>> The operator logs a new pickup record in the database and the dispatcher at the courier division is paged automatically. The dispatcher has an app running on his/her machine that allows them to acknowledge the new pickup (another words, a flag is set on the new pickup record which verifies that the dispatcher has received notification of the new pickup).
>>Now, one of the forms that runs in the background on the client service app queries the database for any new pickup records where the flag has not been set by the dispatcher. If it finds one, the form will become visible and the new pickup record will be listed in a datagrid on the form. Now the client service operator is aware that the dispatcher has not acknowledged the new pickup and the operator can call to find out what the hold up is.
>>The other background form works the same way. The only difference is, it is checking to see if the dispatcher has been notifid by the courier that he/she has a new pickup. If not, this form will become visible on the client service app to notify the operator that the courier does not know about the new pickup.
>>
>>Clear as mud! My explanations are horrible, but I hope you get the point. If you have any more questions, I will be happy to answer them. Hope this helps. Thanks again and have a great day.