Karen,
Probably a
stupid question, but is there a relationship between the order in which the
tables are added to the form and the result of NEXTTAB?
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: Thursday, July 03, 2003 2:51
PM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Multi Table
form
RBWin 1.866
Hope someone can help me on this. This is one of those
deal breakers for a new client of mine. I make it a practice
to never design a form with >2 tables on it (preferring to
have tables off buttons), but in this instance I am trying
to replace a very complicated spreadsheet that the client is
using to calculate billing. There's from 5 - 7 different
'rows' of data individually calculated and added together, and
there's 4 distinct types of calculations. I can easily put
the raw data into one table and have a one-region form, but
I gave up trying to design a formula that would show the
calculation of each row on the form, especially since
some of the calculations depend on previous row calculations!
Anyway, I came up with 4 tables to hold the data, each with
a simple computed column for the calculation. I designed a
4-table form. Only one field from each row is editable,
the others are display only. It ALMOST works perfectly!
The problem is movement within the form.
If my 4-table form had no regions in it, movement works fine.
Pressing [enter] after each field brings you right down into
the next table. But the first table is a 2-row region.
After pressing [enter] after the last row, you hear a beep
and you do not go to the next table, which also happens to
be a region. If I press a [shift][F8] from that field, I go
to the next table, but I know the client won't like that
because they're used to simply arrowing around the
spreadsheet.
So I put an exit eep from the field that says if you're on
that last row (I know by looking at the description of the
row) do a 'NEXTTAB'. The problem is that it skips down
2 tables! I replaced it with a playback of [Shift][F8] and
it does the same thing. At that point things get really
screwy and if I manually start doing [shift][f8] and [f7]
eventually I will get kicked out of RBase.
Any brainy ideas that I can try? This may blow my project
if the client isn't able to easily move through this
'simple looking' 7-row form.
Karen
