Hi Leland,

Thanks for your reply! I will definitely take a look at it. I am working with an Accounting package called Visual Accountmate, which uses a mix of rv's, spt, and sp's, but mostly rv's. For changes to existing code, for the most part I have to work within their existing framework, but for new modules, I can start to use SPT, SP's almost exclusively.

Re: not rebuilding the grid, I am employing a similar technique. In the load of my form I do a sqlexec with a 'select *' for each relevant table, to get a cursor that returns no rows, but contains the complete structure in a vfp cursor. Then I use:

afields(lamytable)
create cursor mytable from array lamytable

then set the properties to make it updatable. Then I use this cursor for all my data manipulation. I am also zapping the cursor whenever I need to reexecute the query, instead of closing it. I had read some other posts here about some techniques for preserving the grid, and preventing it from getting rebuilt, but they seemed cumbersome, and there was some doubt in my mind as to whether they would work reliably, so I have decided to go with this method as well.

I will take a look at your site within the next few days and get back to you with feedback.

Thanks again

>Hi David,
>
>I have written an example app using VFP 7 as a front-end client to connect to a postgres back-end server. The app is based entirely on SPTs, and include techniques to place the cursor into a table. If a new SQL is executed, the new cursor is fetched, the table is zapped, and the cursor is again copied into the table. The grid's record source is the table which is zapped instead of close; therefore, the grid never need be rebuilt because its recordsource is never lost.
>