Then I think Mike's on the right path, wrapping any GO command in a try..catch.
--
rk
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Fred Taylor Sent: Monday, May 08, 2017 5:26 PM To: profoxtech@leafe.com Subject: Re: Question about determining when record not showing after filter applied
GO recordno does not honor the filter. You can still go to a filtered record (or deleted).
Fred
On Mon, May 8, 2017 at 1:50 PM, Richard Kaye rkaye@invaluable.com wrote:
Yep. Store the recno to a memvar before you set the filter. GO memvar. Check for EOF. You'll probably want to set lockscreen while you're doing all that stuff.
--
rk
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of mbsoftwaresolutions@mbsoftwaresolutions.com Sent: Monday, May 08, 2017 4:49 PM To: profoxtech@leafe.com Subject: Re: Question about determining when record not showing after filter applied
On 2017-05-08 16:45, Fred Taylor wrote:
You have to move the record pointer to get the filter to "kick in". You might try SKIP 1 IN yourtable and SKIP -1 IN your table and see if you come back to the same record # you started at.
Fred
Hi Fred (and Richard!),
That sounds like a workable plan. It'd help if I had a Key field but I don't; still, RECNO('myCursor') should suffice and tracking my spot and verifying if it was affected.
Thanks!
[excessive quoting removed by server]