|
If you are retrieving a lot of rows, you can use retrieveAsNeeded.
Whenever I think I need retrieveAsNeeded, I always rethink what I am doing...
does the user need (or even want) to see all those? I often add criteria
that limits the data (by customer number, by date, etc.)... you can also find
some kind of grouping and create an explorer-type interface with a tree on the
left and the data on the right... orders by region-territory-customer for
example....
If you are not retrieving a lot of rows and the SQL runs slow, you might
need to examine your SQL... are you doing unnessesary joins? Table
scans? Would an index on the table help? If you are joining to
another table to get a description (state name from the state table since the
customer table only has the state code) you might want to consider a dropdown
datawindow that will display the state name since it will retrieve it only once
for the datawindow and then you can eliminate that join.
If the SQL looks okay, check your code. Are you doing a lot of
unnecessary computations in your datawindow? Do you have any code in the
retrieveRow event? Code in there (even just comments I've heard) slow down
the retrieval.
If all of the above fail, is your network response time slow?
Good luck,
Daniel
|
- PFCSIG How to increase speed when retrieving data into... Andrew Subhagia T.
- RE: PFCSIG How to increase speed when retrieving ... Daniel Coppersmith
- RE: PFCSIG How to increase speed when retrieving ... Griffith, Daniel M.
- Re: PFCSIG How to increase speed when retrieving ... richard . frantz
- Re: PFCSIG How to increase speed when retrieving ... Rajkumar Chilamula
