Hi Len,
Klaus,
It seems that you come from an old fashioned DB background (i.e.,
dBaseII, etc) where the idea of a record number meant something.
Actually I come form nowhere (database wise) :-D
And I really do not care about record numbers, I only want to display
something like
Record
On 10/23/08 3:45 PM, Klaus Major [EMAIL PROTECTED] wrote:
Hi Klaus,
Strastwutje Ruslan,
Gutten tak,
On 10/23/08 2:55 PM, Jan Schenkel [EMAIL PROTECTED] wrote:
--- Klaus Major [EMAIL PROTECTED] wrote:
Hi all,
1. One can move to the first/prev/next/last record
in a DB cursor with:
On 10/24/08 10:29 AM, Klaus Major [EMAIL PROTECTED] wrote:
It seems that you come from an old fashioned DB background (i.e.,
dBaseII, etc) where the idea of a record number meant something.
I will argue to Len.
1) Klaus did asked about random POSITION of cursor.
2) about how to find it again
Hi Ruslan,
On 10/23/08 3:45 PM, Klaus Major [EMAIL PROTECTED] wrote:
Hi Klaus,
Strastwutje Ruslan,
Gutten tak,
Oh, you also speak Polish :-D
Just kidding.
...
Some good news for Klaus :-)
Valentina for Revolution, allows random move on cursor records,
It have method
Vcursor_Position( N
On Oct 23, 2008, at 8:33 PM, Len Morgan wrote:
Klaus,
It seems that you come from an old fashioned DB background (i.e.,
dBaseII, etc) where the idea of a record number meant something. If
you
read up on the history of SQL, you'll see that one of reasons for SQL
was to get rid of the
Hi all,
1. One can move to the first/prev/next/last record in a DB cursor
with: revdb_moveXXX(Cursor_ID)
Is it also possible to go to a specific record NUMBER? Maybe I
overlooked this in the docs...
2. Since I cannot test it in the moment, how can one check if an
existing table does NOT
--- Klaus Major [EMAIL PROTECTED] wrote:
Hi all,
1. One can move to the first/prev/next/last record
in a DB cursor
with: revdb_moveXXX(Cursor_ID)
Is it also possible to go to a specific record
NUMBER? Maybe I
overlooked this in the docs...
Nope, you have to look at
Hi Jan,
--- Klaus Major [EMAIL PROTECTED] wrote:
Hi all,
1. One can move to the first/prev/next/last record
in a DB cursor
with: revdb_moveXXX(Cursor_ID)
Is it also possible to go to a specific record
NUMBER? Maybe I
overlooked this in the docs...
Nope, you have to look at
On 10/23/08 2:55 PM, Jan Schenkel [EMAIL PROTECTED] wrote:
--- Klaus Major [EMAIL PROTECTED] wrote:
Hi all,
1. One can move to the first/prev/next/last record
in a DB cursor
with: revdb_moveXXX(Cursor_ID)
Is it also possible to go to a specific record
NUMBER? Maybe I
overlooked this
On 10/23/08 2:55 PM, Jan Schenkel [EMAIL PROTECTED] wrote:
2. Since I cannot test it in the moment, how can one check if an existing
table does NOT contain any data/records (yet)? I presume one can get a db
cursor first and then check revdb_recordcount = 0. Is that correct?
Depending on
Strastwutje Ruslan,
On 10/23/08 2:55 PM, Jan Schenkel [EMAIL PROTECTED] wrote:
--- Klaus Major [EMAIL PROTECTED] wrote:
Hi all,
1. One can move to the first/prev/next/last record
in a DB cursor with: revdb_moveXXX(Cursor_ID)
Is it also possible to go to a specific record
NUMBER? Maybe I
Klaus,
It seems that you come from an old fashioned DB background (i.e.,
dBaseII, etc) where the idea of a record number meant something. If you
read up on the history of SQL, you'll see that one of reasons for SQL
was to get rid of the concept of a record number. In fact when you join
two
12 matches
Mail list logo