I am upgrading to VFP8 and would like some advice on the following scenario.
I have 2 applications (one a stand alone app we will call A and a web app
called B) A does all of the work driving real time hardware with a regular
vfp form based interface. This interface is extended to the web server via
B. Now B never relies on A for anything. They share the same data although
buffered for B. B however does receive requests from the web interface which
must be passed to A, these requests must be processed immediately as they
may control some piece of hardware. B requires no response from A other than
to say it recieved the request.
My question then is this.
Am I better off keeping the two apps seperated and communicate between the
two with COM events, or should they be one app that shares all of the
duties?

Thanks in advance,
jrg

Re: Strategy suggestions please by Hans

Hans
Thu Nov 06 07:52:08 CST 2003

I think you should keep them separated.
If you want to avoid COM events, you can use a timer event in A that polls
the database for requests coming in and starts processing.

Hans


"James Grapes" <jrg@nospam_hardynet.com> wrote in message
news:#ND0ARGpDHA.2592@TK2MSFTNGP10.phx.gbl...
> I am upgrading to VFP8 and would like some advice on the following
scenario.
> I have 2 applications (one a stand alone app we will call A and a web app
> called B) A does all of the work driving real time hardware with a regular
> vfp form based interface. This interface is extended to the web server via
> B. Now B never relies on A for anything. They share the same data although
> buffered for B. B however does receive requests from the web interface
which
> must be passed to A, these requests must be processed immediately as they
> may control some piece of hardware. B requires no response from A other
than
> to say it recieved the request.
> My question then is this.
> Am I better off keeping the two apps seperated and communicate between the
> two with COM events, or should they be one app that shares all of the
> duties?
>
> Thanks in advance,
> jrg
>
>



Re: Strategy suggestions please by James

James
Thu Nov 06 11:22:15 CST 2003

Yes, that is what I have been doing, I was just wondering if there was a
better way. I just have a problem with polling (it seems so ineffecient).
One of the reasons for my curiosity is that I read something about VFP8
being able to handle windows messaging.
Thanks,
jrg

"Hans de Groot" <grooth@wxs.nl> wrote in message
news:OtmO4zGpDHA.2512@TK2MSFTNGP09.phx.gbl...
> I think you should keep them separated.
> If you want to avoid COM events, you can use a timer event in A that polls
> the database for requests coming in and starts processing.
>
> Hans
>
>
> "James Grapes" <jrg@nospam_hardynet.com> wrote in message
> news:#ND0ARGpDHA.2592@TK2MSFTNGP10.phx.gbl...
> > I am upgrading to VFP8 and would like some advice on the following
> scenario.
> > I have 2 applications (one a stand alone app we will call A and a web
app
> > called B) A does all of the work driving real time hardware with a
regular
> > vfp form based interface. This interface is extended to the web server
via
> > B. Now B never relies on A for anything. They share the same data
although
> > buffered for B. B however does receive requests from the web interface
> which
> > must be passed to A, these requests must be processed immediately as
they
> > may control some piece of hardware. B requires no response from A other
> than
> > to say it recieved the request.
> > My question then is this.
> > Am I better off keeping the two apps seperated and communicate between
the
> > two with COM events, or should they be one app that shares all of the
> > duties?
> >
> > Thanks in advance,
> > jrg
> >
> >
>
>



Re: Strategy suggestions please by trw7at

trw7at
Fri Nov 07 11:24:56 CST 2003

James Grapes seemed to utter in
news:uw7doqIpDHA.1096@TK2MSFTNGP11.phx.gbl:

> Yes, that is what I have been doing, I was just wondering if there was
> a better way. I just have a problem with polling (it seems so
> ineffecient).

Any chance of using an INSERT or UPDATE trigger to fire off
the needed processing when B inserts/updates the records?

-- TRW
_______________________________________
My e-mail: t r w 7
@ i x . n e t c o m . c o m
_______________________________________

Re: Strategy suggestions please by James

James
Fri Nov 07 18:41:44 CST 2003

I have not tried that with this project but in the past I have had
unexplained intermittent problems in the past when trying this approach. I
may try again with vfp8.
Thanks,
jrg

"Tim Witort" <trw7at@ixdot.netcomdotcom> wrote in message
news:Xns942C5FCE7FF55timwitortwrotethis@207.217.77.205...
> James Grapes seemed to utter in
> news:uw7doqIpDHA.1096@TK2MSFTNGP11.phx.gbl:
>
> > Yes, that is what I have been doing, I was just wondering if there was
> > a better way. I just have a problem with polling (it seems so
> > ineffecient).
>
> Any chance of using an INSERT or UPDATE trigger to fire off
> the needed processing when B inserts/updates the records?
>
> -- TRW
> _______________________________________
> My e-mail: t r w 7
> @ i x . n e t c o m . c o m
> _______________________________________