Steve,

My first instinct would be to reconsider creating a seperate table for fields that otherwise belong in the AS400 database. Why not add those fields to the AS400 tables? Most of the overhead in accessing data is locating the right records and your design will require the application to do that twice. This means twice the inserts, twice the locates, twice the deletes, etc.

Other than that I would consider moving the data query out of the Load. If you need the structure do a NODATA to keep data from getting pulled and slowing down your form.

Then you could use a timer to grab your first set of data records after the form is open. If you need to check for more records later then I'd only query for new records using a timer set to an interval that works for you.

Greg


>I am looking for some advise on what the best possible way to use VFP as a front end to an AS400 database. Right now I have a mirror of the AS400 database in a VFP table. This makes my queries run faster, but it seems like a waste. I am in the process of revising my app to make it clean, fast, and efficient. I am trying to just use the AS400 to store the data(except in cases where the AS400 database does not have a particular field I need for a record). I have a table which extends the data in these situations. My trouble is the speed has diminished. The SPT is currently pulling approx 67,000 records which takes about 18-20 seconds. Right now I have it running in the Load event of my record display form. How do I handle records being added and or updated almost continually by other users? I can't afford to run the SPT that often. How can this be setup to run with the slightest hesitation?