Re: What kind of Program?
- From: "YYZ" <matt@xxxxxxxxx>
- Date: 11 Aug 2005 14:27:31 -0700
I'm not trying to give you a hard time, but I still don't get it.
Ralph's solution seems good, but still overkill to me. Tell me what
I'm missing in the following situation:
User opens your program, does stuff, then prints a fax to the fax
server, and IMMEDIATELY issues an update to the SQL Server that says
"Yeah, I sent a fax" -- that whole process of updating the SQL Server
would take about 1/10 of a second most likely. Then the user sends
another fax (in your example she did 15) -- so what? The processes are
tied to each other -- print a fax, update SQL Server.
And I really don't understand why anything has to "listen [to[ the fax
printer" -- are you looking to log into SQL Server that a fax was
successfully sent? If that is the case, then create a program to query
the fax server and see what new faxes have been sent. Setup a job on
that server to run it every minute or 10 minutes or 2 hours or
whatever.
Matt
.
- Follow-Ups:
- Re: What kind of Program?
- From: vul
- Re: What kind of Program?
- References:
- What kind of Program?
- From: vul
- Re: What kind of Program?
- From: YYZ
- Re: What kind of Program?
- From: vul
- What kind of Program?
- Prev by Date: Re: OT (Sorta): DLL Registration under Restricted User Mode
- Next by Date: Re: Async Callback (Part 2)
- Previous by thread: Re: What kind of Program?
- Next by thread: Re: What kind of Program?
- Index(es):
Relevant Pages
|
Loading