I'm writing a support desk application for our office. When someone logs a call I'd like to refresh averybody elses screens to reflect the change. I'm using vb6 and sql server 7. The only way I can think of is to use a WinSock control but this seems like an inelegant solution. I've never used VB or SQL Server before so I'm probably overlooking something obvious. Any Ideas?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
How would you do this?
- Thread starter rwilliams
- Start date
There are probably many different ways of doing this.
I would probably have a timer control on the client application, and every now and again use the timer event to query against the database for a the last logged call.
If this value is different to the one they currently have then requery the calls.
It all depends on how essential it is to have instantaneous refresh or whether a couple of minutes delay is acceptable?
I would probably have a timer control on the client application, and every now and again use the timer event to query against the database for a the last logged call.
If this value is different to the one they currently have then requery the calls.
It all depends on how essential it is to have instantaneous refresh or whether a couple of minutes delay is acceptable?
- Thread starter
- #3
thanks, I'll probably do that as a couple of minutes gap would be acceptable. I figure that's how Outlook works so if it's good enough for them...
I'm used to writing in a a 4GL language called Progress and using that you could write a trigger that broadcast a message from the server to anybody connected, but that doesn't seem to be possible in SQL Server. Mind you that's about the only disadvantage I've come across so far.
I'm used to writing in a a 4GL language called Progress and using that you could write a trigger that broadcast a message from the server to anybody connected, but that doesn't seem to be possible in SQL Server. Mind you that's about the only disadvantage I've come across so far.
- Status
