The ‘SELECT * FROM TABLE’ gives you a RowSet, which remains valid until discarded. Adding/modifying a record does not change that RowSet.
The SELECT gives you a RowSet and you then iterate through that, so I’m not sure what you mean by ‘SELECT FROM RS WHERE ID=Integer’. You should be doing ‘SELECT * FROM TABLE WHERE ID=integer’ and then using the resulting RowSet.
How work SELECT. At the first message, I put 4 different URLs that explain in detail the mos common use of SELECT to avoid getting a 5 y/o explanation about SELECT. Some lurkers may ler-arn something, but in my case, I already read that… long time ago to create version 1 of that software, in 2012-2013. Now we are using API 2, things are a bit different.
So, you never navigate (as a user) thru your data base. I do not want to talk about filemaker because I do not used it since the end of the 80s, but this was perfectly possible in View by Record to read since Record n, all Records until Record n = i.
Just what you can do manually with a Rollodex.
The first of those is a typing error on your part. Remove the /.org and try again. At sqite.com (actually sqlite.org) you can find the entire SQL syntax understood by SQLite - including SELECT - Query Language Understood by SQLite. I always go to sqlite.org, where you have a reference (not tutorial) website created by the sqlite devs. Better answers there.
In my case, these are not databases, they are mailboxes. Implemented as an SQLite database, but the user doesn’t care about that. The emails are shown in a listbox and the user can select one to see its contents. At least one of my users has around 1000 mailboxes (I don’t understand how he keeps track of them all).
The mail selected by the user is then displayed below. The user can click on listbox headers to sort the displayed mailbox by that column (done by reloading the entire listbox and having SQLite presenting the results in the right order via an ORDER BY).
A separate search facilty allows the user to search for emails matching a number of criteria across one or many mailboxes.
Our difference here is your user have the list of mail (easy to do), my user do not see the list of people and the navigation is done here.
Or he must close the wRecord window to search in the wLMist window its entry, then double click to open that entry in wRecord.
Assuming your wLMist window contains the listbox that you populated from the query, create a method(s) that you can call from wRecord to return the next or previous ID from the listbox. Increment/Decrement listbox.SelectedRowIndex, retrieve the ID from that row and return it. In wRecord, run a query to retrive just that one record.
Go to a window, choose, double-clik, Opens another window.
NB. Each entry in the list view have its Record ID in Row Tag.
So, In Record View I ask for this Record from the Data Base.
ListBox is here only for display (yes, its a displayer).
`
How many times will you do that before sending the computer thru the window ?
Then you are doing it correctly. There is no overhead or lag. It should be seamless. The user won’t notice at all and your app will experience no ill effects.
