Live response over the web 
Author Message
 Live response over the web

I have a website that people can submit requests from our department,
using ASP and SQL2000. The requests come from all over Florida, and our
department is in multiple locations. Currently, the system emails our
person when a request comes in for him.

I want to create a VB program that is running on our department team's
computers, that pops up (or beeps, or flashes) when someone submits a
new request. Then they can open up this VB program, see what it is, and
click on it (which would open up a browser that they can do more with).

Any help or suggestions to create this program would be helpful. Mainly,
I want to know broad scale, how to approach this.

1) Will the client VB program be connecting straight to the SQL box, or
will there need to be a client VB program and a server VB program?
2) What is the best way to connect to the SQL, DAO, ADO, ODBC, etc.?
3) Which is better, connect directly to the tables, or call Stored
Procedures, from the VB program?



Thu, 06 Jan 2005 06:14:23 GMT  
 Live response over the web

Quote:
> 1) Will the client VB program be connecting straight to the SQL box, or
> will there need to be a client VB program and a server VB program?

You could either have a server application that processes a list of message
requests and forwards the messages to connected client applications through
call-backs, or use client applications that connect directly to the database
and check for new rows every few minutes/seconds. The best answer would
depend on further details but you can do either.

Quote:
> 2) What is the best way to connect to the SQL, DAO, ADO, ODBC, etc.?

I would say ADO using the OLEDB Provider.

Quote:
> 3) Which is better, connect directly to the tables, or call Stored
> Procedures, from the VB program?

I use stored procedures and views when it increases speed, maintainability
and security. For your problem here you can use either. Many companies
insist that access to databases via the internet be done through defined
procedures and views for security reasons.

--
Mike Collier BSc (Hons) - www.adoanywhere.com
ADO Object Browser and COM Server.
Consultancy and Design - ADO & Database Specialists.


Quote:
> I have a website that people can submit requests from our department,
> using ASP and SQL2000. The requests come from all over Florida, and our
> department is in multiple locations. Currently, the system emails our
> person when a request comes in for him.

> I want to create a VB program that is running on our department team's
> computers, that pops up (or beeps, or flashes) when someone submits a
> new request. Then they can open up this VB program, see what it is, and
> click on it (which would open up a browser that they can do more with).

> Any help or suggestions to create this program would be helpful. Mainly,
> I want to know broad scale, how to approach this.

> 1) Will the client VB program be connecting straight to the SQL box, or
> will there need to be a client VB program and a server VB program?
> 2) What is the best way to connect to the SQL, DAO, ADO, ODBC, etc.?
> 3) Which is better, connect directly to the tables, or call Stored
> Procedures, from the VB program?



Thu, 06 Jan 2005 07:31:06 GMT  
 
 [ 2 post ] 

 Relevant Pages 

1. Live response over the web

2. free p2p win32 web server / shares live word data

3. Free SQL Tutorial w/ Live Practice Database - 100% Web Based

4. Live Video on the web using a VB script

5. Free SQL Tutorial w/ Live Practice Database - 100% Web Based

6. Reading XML / SOAP response from call to a Web Service

7. Delayed response from Web Service

8. Response Redirect doesn't Work - No me funciona Response Redirect

9. Copy live data

 

 
Powered by phpBB® Forum Software