I normally call up an Edit Form directly to the record to be edited, such as :
Edit Using FormName Where Column = value
However, while this method is fast, it only obtains one record and one cannot
do a NEXT or PREV function.
I have a requirement to pull up a form starting at record "X", but then be able
to Next or Previous
from that record using a Navigator bar. The table is an Item Master table and
has only
about 4000 rows. A small table.
I have used the Property Table Search before, but in rare cases due to slow
speed.
However in this instance, I must have the ability to call up the form at Record
X and
then move back and forth in the record set.
I must be implementing this function incorrectly as it is extremely slow.
Below is the code I am using:
cls
--display a message
pause 3 using 'Locating Record....Please wait!' +
caption 'Item Master System' +
option gauge_visible on| gauge_color blue|gauge_interval 10
--Create command line
SET VAR vSearchString TEXT = NULL
SET VAR vSearchString = +
('PROPERTY TABLE ItemMaster SEARCH->Item->'+.vItem)
--conduct search
&vSearchString
I put the PAUSE message there to inform the user the computer is
not locked up as this method often takes minutes to pull up the
record. The column ITEM is an indexed record and in a single table form.
This form displays fields in the form via direct field placement. No scrolling
regions, grids or listviews can be used in this instance as the data will not
be displayed in a tabular form and one record per "screen / page" will be
displayed.
I need to place this function in a "Go To Item" Button EEP as well, so the user
can be at Item 100 and jump directly to Item 3500 and then have the ability to
PREV / NEXT from that spot. I have seen this type of function in other programs
and know RBase can do anything the others can!
Any thoughts are appreciated.
Thanks,
Bob
