>Thanks Gary!

No problem.

>Do you make frequent use of this type of cursor.

I used it quite a bit when I was using Codemine against local data. I haven't used Codemine for any recent development - my last significant Codemine work has been against SQL server for the past few years.

>It seems like the most flexible both from querying and upsizing?

I found some nice ways to use this cursor. I liked it mostly because it was just like having an ad-hoc SQL statement but, I could view it as a cursor object and, I could link it in automated requerying using Codemine's RI in the CDE.

One thing to note though; if you use LSQLPT cursor, when they are requeried, the existing underlying native Fox cursor is closed and a new one re-opened, possibly in another work area. Remember, if you base a grid on an LSQLPT cursor, when you requery the cursor, the grid's recordsource is snatched away so, you will have to code against this or have blank grids staring back at you when you requery. Also, LSQLPT cursors are read-only. So, if you can live with these restrictions, great. But, they are no substitute for views, local, remote or otherwise. With a local view, you can requery and your cursor doesn't change so, OK with grids - also, views can update their datasources if you want them to.

HTH