If you need to remove deleted records, ie issue a pack, on the readwrite

cursor this will do the trick.

SELECT * FROM CursorName WHERE NOT DELETED() INTO CURSOR CursorName

READWRITE.

Voila! Cursor has no deleted records.

Caveat! If the cursor is tied to a grid, you may find that all of your

grid settings go away. Look up "SAFE SELECT" article on UT to have a way

get around this issue.

HTH,

Mike

> Thanks Vince & Lew!

>

> I just found this line in the VFP helpfile:

> "NOFILTER creates a cursor that can be used in subsequent queries."

>

> So it would seem READWRITE NOFILTER is the proper equivalent to INTO

> TABLE..

>

> -Steve

>

>

> At 09:56 PM 07/29/2010, you wrote:

>>Steve Ellenoff wrote:

>> > Is there any difference between these two?

>> >

>> > I'm looking at some older code and I have remarks about the SELECT

>> > SQL using INTO TABLE to avoid some VFP errors that says something

>> > like, "Command cannot be issued on a cursor" or something to that

>> effect.

>> >

>> > Would changing my code to CURSOR READWRITE work equally well as the

>> > INTO TABLE ?

>>

>>If you used tables to avoid "operation can not be performed on a

>>cursor," I would think you could do CURSOR READWRITE, followed by USE

>>DBF("MyCursor") ALIAS Bob, and do whatever on Bob. Just off the top of

>>my head.

>>

>>

>>

[excessive quoting removed by server]

_______________________________________________

Post Messages to: ProFox@leafe.com

Subscription Maintenance: http://leafe.com/mailman/listinfo/profox

OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech

Searchable Archive: http://leafe.com/archives/search/profox

This message: http://leafe.com/archives/byMID/profox/4ca3ff03bcdef23fcf61606fed7c5509.squirrel@www.webmail.execulink.com

** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.