the Old Set Follow

I don't believe we still have the SET FOLLOW ON / OFF?

A rowset property would be huge for me.

The absense of SET FOLLOW has caused me more headache than I want to admit 
:-)

I have allot of places in my app where a user will be editing data that is 
either constrained by a conditional index, filter or sql statement.  In 
those cases when a user commits a row that no longer fits in the the rowset 
it sends the rowset to endOfSet or begining of set.

Yes I found ways around it but it is not always as simple as bookmark() 
goto()

Thank you

Greg Hill

Greg Hill wrote:
> I don't believe we still have the SET FOLLOW ON / OFF?
> 
> A rowset property would be huge for me.
> 
> The absense of SET FOLLOW has caused me more headache than I want to admit

> :-)
> 
> I have allot of places in my app where a user will be editing data that is

> either constrained by a conditional index, filter or sql statement.  In 
> those cases when a user commits a row that no longer fits in the the rowset

> it sends the rowset to endOfSet or begining of set.
> 
> Yes I found ways around it but it is not always as simple as bookmark() 
> goto()

Um, have you looked at the navigateByMaster and navigateMaster methods 
of the rowset?

These were created to give the kind of control I believe you're looking for.

Ken

-- 
/(Opinions expressed are purely my own, not those of dataBased
Intelligence, Inc.)/

*Ken Mayer* [dBVIPS]
/Golden Stag Productions/
dBASE at goldenstag dot net
http://www.goldenstag.net/dbase/dBASEBook.htm
http://www.goldenstag.net/dbase/dBASEReportsBook.htm
http://www.goldenstag.net/GSP

"Ken Mayer [dBVIPS]" <dbase@_nospam_goldenstag.net> wrote in
message 
news:12wLawNYHHA.1796@news-server...
> Greg Hill wrote:
>> I don't believe we still have the SET FOLLOW ON / OFF?
>>
>> A rowset property would be huge for me.
>>
>> The absense of SET FOLLOW has caused me more headache than I want to 
>> admit :-)
>>
>> I have allot of places in my app where a user will be editing data that

>> is either constrained by a conditional index, filter or sql statement.

>> In those cases when a user commits a row that no longer fits in the the

>> rowset it sends the rowset to endOfSet or begining of set.
>>
>> Yes I found ways around it but it is not always as simple as bookmark()

>> goto()
>
> Um, have you looked at the navigateByMaster and navigateMaster methods of 
> the rowset?
>
> These were created to give the kind of control I believe you're looking 
> for.

Yes and that is not what I am after.

Ken, I think your referring to SET SKIP TO,  that is not at all what I am 
looking for.

I am talking about SET FOLLOW ON/OFF, it was in the DOS versions of dBASE, I 
guess you never used it?
The only thing I found on a google of it is as follows, but it was a very 
handy tool.

http://groups.google.com/groups/search?hl=en&ie=UTF-8&oe=UTF-8&q=%22
set+follow+on%22%2Bdbase

Greg Hill

"Ken Mayer [dBVIPS]" <dbase@_nospam_goldenstag.net> wrote in
message
news:12wLawNYHHA.1796@news-server...
> Greg Hill wrote:
>> I don't believe we still have the SET FOLLOW ON / OFF?
>>
>> A rowset property would be huge for me.
>>
>> The absense of SET FOLLOW has caused me more headache than I want to 
>> admit :-)
>>
>> I have allot of places in my app where a user will be editing data that

>> is either constrained by a conditional index, filter or sql statement.
In 
>> those cases when a user commits a row that no longer fits in the the 
>> rowset it sends the rowset to endOfSet or begining of set.
>>
>> Yes I found ways around it but it is not always as simple as bookmark()

>> goto()
>
> Um, have you looked at the navigateByMaster and navigateMaster methods of 
> the rowset?
>
> These were created to give the kind of control I believe you're looking 
> for.

Yes I have, its not even close.  SET FOLLOW ON/OFF is not related to 
relationships at all.

Ken, I think your referring to SET SKIP TO?

I am talking about SET FOLLOW ON/OFF, it was in the DOS versions of dBASE.

As I say if you have a filter on a table and you change the data so that it 
does not fit in the filter, your record pointer goes to EOF or out of range.
It takes a refresh(), go first() to bring it back.  I use bookMark and 
unique record #'s along with notifyControls and even API call to hide 
somethings that just won't hide with notifyControls, all that in order to 
get back where it left off.

The only thing I found on a google of it is as follows, but it was a very
handy tool.

http://groups.google.com/groups/search?hl=en&ie=UTF-8&oe=UTF-8&q=%22
set+follow+on%22%2Bdbase

Greg Hill

NOTE:  The Browse Class has the follow property that is non-functional as 
dBASE documented that some properties would be carried over just for 
compatibility or should I say to prevent error of old code.
You won't see that property unless you drop the object on a form and look 
through the properties.

Just to clarify, that is my wish :-) I want it back.....

Thank you

Greg Hill

"Greg Hill" <ghill123@hotmail.com> wrote in message 
news:esm72k.1kg.1@news.alldbase.com...
>I don't believe we still have the SET FOLLOW ON / OFF?
>
> A rowset property would be huge for me.
>
> The absense of SET FOLLOW has caused me more headache than I want to admit

> :-)
>
> I have allot of places in my app where a user will be editing data that is

> either constrained by a conditional index, filter or sql statement.  In 
> those cases when a user commits a row that no longer fits in the the 
> rowset it sends the rowset to endOfSet or begining of set.
>
> Yes I found ways around it but it is not always as simple as bookmark() 
> goto()
>
> Thank you
>
> Greg Hill
>
>