[solved] USE and SEEK / SEEK () as the target

Hi there! :)

It's very confusing and Lianja is not doing what I expect and understand from the documentation.
The goal is simple: Open the table and search for a data record with LOCATE, SEEK / SEEK().

So roughly:

Code:

---

OPEN DATABASE
USE tabel
LOCATE / SEEK / SEEK()
BROW

---

As an example here is the Lianja Southwind database.

OPEN DATABASE SOUTHWIND // for all further lines

USE table in 0 ALIAS MyTable -> table is open

LOCATE FOR customerid = "EASTC" -> No error message
BROW -> Shows the first record, not the 19th!

SET ORDER TO customerid -> No error message
SEEK("EASTC", MyTable) -> Error message: "')' was expected"
SEEK("EASTC") -> No error message
BROW -> Shows the first record, not the 19th!

SET ORDER TO customerid -> No error message
seek "EASTC" -> no error message
BROW -> Shows the first record, not the 19th!

I have already tried all types of play with '"' and parameters, etc. NOTHING leads to the goal. I have not written down all attempts here.

BTW: Why does Lianja no longer know my table when I switch to DATA WORKSPACE in between and look at the table there? Must that be possible? Sometimes, when the table is open in the console, Lianja also shows me in Data WORKSPACE: "File 'customers.dbf' does not exist".
What ??? Can I only go back to the table when I close all databases in DATA WORKSPACE ("X" in the toolbar) and open them again?

Sorry, but sometimes I start to wonder if anyone on the data side is working with VFP-script here ... :-(

In any case, I would be grateful for a few hints that go beyond the 3 lines in the documentation and reveal connections between the various commands / functions.
It's no fun like that ...

Thanks a lot in forehand! :)

I am not a fan of noSQL and BROWSE, but try this:

Code:

---

LOCATE FOR customerid = "EASTC"
?found()
.T.

BROWSE for customerid = "EASTC"

set order to customerid
SEEK "EASTC"
?found()
.T.

?seek("EASTC",mytable)
.T.

---

Quote:

---

Originally Posted by josipradnik

I am not a fan of noSQL and BROWSE, but try this:

[CODE]LOCATE FOR customerid = "EASTC"
?found()
.T.

BROWSE for customerid = "EASTC"

set order to customerid
SEEK "EASTC"
?found()
.T.

?seek("EASTC",mytable)[
.T./CODE]

---

I have to do it like this not in an App. It's just a script to import data from other tables...

All you !found() works, but not a BROWSE after a search. Why does the record pointer ist not on the record I searched for? A normal browse starts every time with the first record. I can't believe it's supposed to be like that. Then why would you need a browse?

For example a BROWSE FOR ... is umpteen times slower than a SEEK and then a BROWSE, like I can do it in VFP... In this case I don't need the BROWSE in the script, but to check if my pointer is right, I want to browse...

Lianja's BROWSE is rudiment and is shown modal.
So you cannot move the pointer like in VFP old days when BROWSE played the main role of UI.

Hi Stefan,

The Browse in Lianja shows the cursor, unlike VFP where it brings you to the record. If you were to ? customerid from the Command Window, you would see the correct data. Also the BROWSE FOR doesn't seem to take advantage of the index tags. The VFP "browse" was a special creature all its own, for sure.

Hank

Use index key restriction before browsing.

https://www.lianja.com/doc/index.php/SET_KEY

Set order to customerid
set key to range "EASTC","XXXXX" // all keys >= are included
// set filter to Expr to apply optional filtering within the key range
browse

alternatively browse has a lot of additional built-in functionality:

browse key "eastc"

or

browse key "bergs" for contacttitle="owner"

or

browse splitbar

Attachment 2366

Use it for pick lists...


browse key "bergs" for contacttitle="owner" splitbar title "Customer list" caption "Select a customer"

Attachment 2367

Attachment 2368

Restrict what the user can do...


browse noappend nodelete noedit key "bergs" for contacttitle="owner" splitbar title "Customer list" caption "Select a customer"

Attachment 2369


All CRUD operations are controlled by the business rules in the data dictionary.

Browse is hardly rudimentary.

Also...

seek "bergs"
edit

Attachment 2370

seek "bergs"
edit title "Edit Customers" caption "Customer"

Attachment 2371

hi Stefan,
I also started Lianja as a VFP user and that is a very strange difference. I think BROWSE always starts from the "first" record (depending on the order and the filter). If you are using BROWSE NOWAIT, you can set the record pointer after the grid appears.
If you use a GRID, there is a grid.goto() method that you can use to move poiter to the desired record.

Quote:

---

Originally Posted by strato

hi Stefan,
I also started Lianja as a VFP user and that is a very strange difference. I think BROWSE always starts from the "first" record (depending on the order and the filter). If you are using BROWSE NOWAIT, you can set the record pointer after the grid appears.
If you use a GRID, there is a grid.goto() method that you can use to move poiter to the desired record.

---

Not correct.

See my reply for a solution.

Quote:

---

Originally Posted by HankFay

Hi Stefan,

The Browse in Lianja shows the cursor, unlike VFP where it brings you to the record. If you were to ? customerid from the Command Window, you would see the correct data. Also the BROWSE FOR doesn't seem to take advantage of the index tags. The VFP "browse" was a special creature all its own, for sure.

Hank

---

See my reply for a solution.

Ah! Thanks to everyone!
So far I have assumed that the same commands/functions will also work the same, unless the documentation states something else.
Unfortunately, BROWSE doesn't say that it always shows from the beginning.

Doesn't matter, it would only be nice if deviations are noted in the description of VFP script commands and functions.
Otherwise at some point you will go nuts. ;-)

Thanks again! :-)