>Hi Bob Lee, I took a look at the VFP SELECT SQL help in the VFP Doc. That was your first mistake, VFP- sql is not standard, and wont help in getting fewer records down from the server anyway... use the VFP - sql only when absolutly necessary once you have a few cursors, and need to put them together or something. ) but doing things right, where the server does it, there shouldn't be much reason to mess arround with vfp - version of sql.
Back to the right track. I then took a look for something similar in postgres. Postgres has a [LIMIT count] function that can be included in the SQL, so I added this to my VFP client app with a LIMIT 500. Great ... !!
As far as if this is the right amount, I would say as a demo, it would be a great example, of what speed one could expect to get when they download 500 records from a server over the intenet, (for me with a dsl 768K ) Its going to be quick, but a dialup... maybe not as quick as you would like, But showing for the purpose of a demo what the seed of querries at limit 500 and limit say 50 and limit of 5,000 Will surly tell a story..
Personally, what could a user do with 500 records of anything on a screen ? Cant read them, cant even manage them really. maybe browse through.. ... wasting time. and all that. I tend to put large cursors, where tons of records are being viewed in like a report, where the idea is they print out these mass's of data, and not work with them on the screen. Working with more than a handful of records in a cursor , is (now its just an opinion) ... Sloppy, and leads to data problems do they check back in the data... ?
Usually a user wants to search for something, and when they find it, give them as much of those records as you can.. ! but when they are looking Keep the cursor results down.... so your app appears FAST! and it is... 10- 100 say customer records over the net at 28.8 in 1 second ... is fast.. 500 records... Well then the net begins to show itself.
Bob Lee
In the beginning, there was a command prompt, and all was well.
