David Mustard
Member
I have a question on the above - I have a project going which is an intranet
front end for an Accounts Receivable package. Using WSnap to generate input
and browse features on the ORACLE tables, generate input and pass this
through an interface to the A/R package.
I have a WebDebugger app running through the Web Debugger - it runs
incredibly slowly - minor queries seem to take forever, page
changes/refreshes take "days" (maybe I exaggerate here) but the whole thing
seems to run throught glue. Same with a "beta" CGI version on the intranet.
Yet when I put together exactly the same queries through a "normal" (ie:
non-web based) application the thing runs like magic, ie: all queries and
movement between forms is snappy.
I have tried both Direct Oracle Access AND ODBC with both giving me same
results (Web based and Windows based). Is there something I'm missing in
optimising Web snap for Oracle or is it giving enormous hits on performance.
Like I say above it's only applicable to WebSnap stuff - not to normal
Delphi Apps.
Also - I need to make several queries on reference tables to produce
population for drop down edits so that they are ready and available when the
page in question shows, ie: the OPTIONS have to be in place before the page
generates. I'm doing this through List Adapters and linking them to the
controls - but when is the best time to do this? When the page is first
being created? or is there a more optimum time to do this?
I know - I should read the new Borland documentation (and I will as soon as I finish
this) but I wanted to try the group as well for ideas on both of these
problems
Grateful for any tidbits of information -
Thanks in advance,
------------------
cheers
David Mustard
d.m.mustard@chello.nl
front end for an Accounts Receivable package. Using WSnap to generate input
and browse features on the ORACLE tables, generate input and pass this
through an interface to the A/R package.
I have a WebDebugger app running through the Web Debugger - it runs
incredibly slowly - minor queries seem to take forever, page
changes/refreshes take "days" (maybe I exaggerate here) but the whole thing
seems to run throught glue. Same with a "beta" CGI version on the intranet.
Yet when I put together exactly the same queries through a "normal" (ie:
non-web based) application the thing runs like magic, ie: all queries and
movement between forms is snappy.
I have tried both Direct Oracle Access AND ODBC with both giving me same
results (Web based and Windows based). Is there something I'm missing in
optimising Web snap for Oracle or is it giving enormous hits on performance.
Like I say above it's only applicable to WebSnap stuff - not to normal
Delphi Apps.
Also - I need to make several queries on reference tables to produce
population for drop down edits so that they are ready and available when the
page in question shows, ie: the OPTIONS have to be in place before the page
generates. I'm doing this through List Adapters and linking them to the
controls - but when is the best time to do this? When the page is first
being created? or is there a more optimum time to do this?
I know - I should read the new Borland documentation (and I will as soon as I finish
this) but I wanted to try the group as well for ideas on both of these
problems
Grateful for any tidbits of information -
Thanks in advance,
------------------
cheers
David Mustard
d.m.mustard@chello.nl
