|
Home > Archive > Getting Started with dBASE > February 2006 > Locate
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
|
| I met some random problems with the "LOCATE" command (table appearing being locked into a filter : a browse in testing showing only the rows matching the "for" conditions). I m using the DBASE PLUS V2.1 version.
Any fix on this command since then ?
Thanks for information
Dominique
| |
| Roland Wingerter 2006-02-13, 7:23 am |
| Hi Dominique,
"DLIT" wrote
>I met some random problems with the "LOCATE" command (table appearing being
>locked into a filter : a browse in testing showing only the rows matching
>the "for" conditions). I m using the DBASE PLUS V2.1 version.
> Any fix on this command since then ?
-------
I don't think so, since dBASE Inc. made it clear in the past that the old
xbase commands will not be updated.
However you may want to check the document posted by Jim Sare, Subject
"Product Change Lists Through PLUS v2.50" in the dbase.binaries newsgroup on
Nov. 28, 2004.
Roland
| |
| Ken Mayer [dBVIPS] 2006-02-13, 9:23 am |
| DLIT wrote:
> I met some random problems with the "LOCATE" command (table appearing being locked into a filter : a browse in testing showing only the rows matching the "for" conditions). I m using the DBASE PLUS V2.1 version.
> Any fix on this command since then ?
I am not sure what you expect. If you have filtered the data, a LOCATE
*should* only find matches in the filtered data ...
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/GSP
http://www.goldenstag.net/dbase
| |
|
| Hi Roland, thanks for info
Dom
Roland Wingerter Wrote:
> Hi Dominique,
>
> "DLIT" wrote
> -------
> I don't think so, since dBASE Inc. made it clear in the past that the old
> xbase commands will not be updated.
>
> However you may want to check the document posted by Jim Sare, Subject
> "Product Change Lists Through PLUS v2.50" in the dbase.binaries newsgroup on
> Nov. 28, 2004.
>
> Roland
>
>
| |
|
| This is not the case. There is an actual random bug on this command. It works as follows. The bug does not appear in the command mode but in the progamm mode in certain conditions.
If the locate command when first used it works but if I do some manipulation in the file such as skipping upwards or onwards to look for some data, then the table get locked as if the "for" conditions of the "locate" command had, in the meantime, applied
a filter on this table.
I noticed this by some odd results in my programs and then could check this state by interrupting the program and studying the state of the table. I tried some "set filter to" command but quite unoperative.
I don t understand why dbase has left this type of current command in a "forget it" bag this way. Whatever is the interest of new commands, so said "old ones" have still their interest in my opinion and anyway this type of bug does not make me feel dbase
quite healthy and secure. If the "old" commands don t work well, why the "new" ones should ?
Dom
Ken Mayer [dBVIPS] Wrote:
> DLIT wrote:
>
> I am not sure what you expect. If you have filtered the data, a LOCATE
> *should* only find matches in the filtered data ...
>
> 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/GSP
> http://www.goldenstag.net/dbase
| |
| Ken Mayer [dBVIPS] 2006-02-17, 7:24 am |
| DLIT wrote:
> This is not the case. There is an actual random bug on this command.
> It works as follows. The bug does not appear in the command mode but
> in the progamm mode in certain conditions.
I sometimes still use the old XDML commands, and have never seen this
behavior.
> If the locate command when first used it works but if I do some
> manipulation in the file such as skipping upwards or onwards to look
> for some data, then the table get locked as if the "for" conditions
> of the "locate" command had, in the meantime, applied a filter on
> this table.
That shouldn't happen, but I couldn't tell you why it is ... is it
possible that something in your code is doing this?
> I don t understand why dbase has left this type of current command in
> a "forget it" bag this way. Whatever is the interest of new commands,
> so said "old ones" have still their interest in my opinion and anyway
> this type of bug does not make me feel dbase quite healthy and
> secure. If the "old" commands don t work well, why the "new" ones
> should ?
Can you produce a turnkey example of this and post it in bug-reports for
the R&D team to look at?
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/GSP
http://www.goldenstag.net/dbase
| |
|
| Thanks for your interest. I ve been working with dbase for more than 20 years and wrote over 1000 prgs. I ve never met this bug in DOS versions and I tried to find out the error myself. Ok I ll exract a example and submit it.
Dom
Ken Mayer [dBVIPS] Wrote:
> DLIT wrote:
>
> I sometimes still use the old XDML commands, and have never seen this
> behavior.
>
>
> That shouldn't happen, but I couldn't tell you why it is ... is it
> possible that something in your code is doing this?
>
>
> Can you produce a turnkey example of this and post it in bug-reports for
> the R&D team to look at?
>
> 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/GSP
> http://www.goldenstag.net/dbase
| |
|
| Further to you advice, I posted an example under the label 'LOCATE BUG" in the bugs reports directory
Dom
Ken Mayer [dBVIPS] Wrote:
> DLIT wrote:
>
> I sometimes still use the old XDML commands, and have never seen this
> behavior.
>
>
> That shouldn't happen, but I couldn't tell you why it is ... is it
> possible that something in your code is doing this?
>
>
> Can you produce a turnkey example of this and post it in bug-reports for
> the R&D team to look at?
>
> 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/GSP
> http://www.goldenstag.net/dbase
|
|
|
|
|