It would be possible to write a prc that has the look and feel of a pqa, but
this isn't really what I am looking for. A palmcall to a prc that populates
the <form> fields with data (such as address info) has several advantages,
mostly being development time since the prc could be reused in other pqa's.
And a pqa is much quicker/easier to develop than an prc (so that another
person could use this prc without any programming knowledge). Also it would
save space in the user's ram, since the code to populate the form would only
be installed once then shared.
the prc -> pqa model still has the flaw of requiring two items to be
installed on the client's end, but with a pqa -> prc design, I can hide the
prc from the user (I'm not sure you can hide a pqa -- I'll have to look into
that). The big plus is that a pqa automagicaly install into the palm.net
group, and therefore the user all ready understands that it is a wireless
app.
What I am trying to do has been done. If you haven't seen it check out the
ePQA app by Stevens creek software -- it comes with the source to the pqa.
Mike
"Fitzpatrick, Joe" <[EMAIL PROTECTED]> wrote in message
news:4191@palm-dev-forum...
>
> Sorry, I misunderstood. I thought you wanted to get results from a
> Query and create DB records from them. It is pretty straightforward to
> submit your own request from your PRC and stick the results in a PQA's
> cache. Would that work for you or do you really need to mix (ie, part
> is a PQA form, part is provided by a PRC)?
>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
