> because they're used to simply arrowing around the > spreadsheet. Karen,
Could you map [Shft][F8] to the [Down] arrow? Ben Petersen On 3 Jul 2003, at 15:50, [EMAIL PROTECTED] wrote: > --part1_d.14555d53.2c35e317_boundary > Content-Type: text/plain; charset="US-ASCII" > Content-Transfer-Encoding: 7bit > > > 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 > > > > > > --part1_d.14555d53.2c35e317_boundary > Content-Type: text/html; charset="US-ASCII" > Content-Transfer-Encoding: quoted-printable > > <HTML><FONT FACE=3Darial,helvetica><FONT SIZE=3D2 FAMILY=3D"FIXED" = > FACE=3D"Courier New" LANG=3D"0"><BR> > RBWin 1.866<BR> > <BR> > Hope someone can help me on this. This is one of those<BR> > deal breakers for a new client of mine. I make it a practice<BR> > to never design a form with >2 tables on it (preferring to<BR> > have tables off buttons), but in this instance I am trying<BR> > to replace a very complicated spreadsheet that the client is<BR> > using to calculate billing. There's from 5 - 7 different<BR> > 'rows' of data individually calculated and added together, and <BR> > there's 4 distinct types of calculations. I can easily put<BR> > the raw data into one table and have a one-region form, but<BR> > I gave up trying to design a formula that would show the<BR> > calculation of each row on the form, especially since<BR> > some of the calculations depend on previous row calculations!<BR> > <BR> > Anyway, I came up with 4 tables to hold the data, each with<BR> > a simple computed column for the calculation. I designed a<BR> > 4-table form. Only one field from each row is editable,<BR> > the others are display only. It ALMOST works perfectly!<BR> > The problem is movement within the form. <BR> > <BR> > If my 4-table form had no regions in it, movement works fine.<BR> > Pressing [enter] after each field brings you right down into<BR> > the next table. But the first table is a 2-row region. <BR> > After pressing [enter] after the last row, you hear a beep<BR> > and you do not go to the next table, which also happens to<BR> > be a region. If I press a [shift][F8] from that field, I go<BR> > to the next table, but I know the client won't like that<BR> > because they're used to simply arrowing around the <BR> > spreadsheet.<BR> > <BR> > So I put an exit eep from the field that says if you're on<BR> > that last row (I know by looking at the description of the<BR> > row) do a 'NEXTTAB'. The problem is that it skips down<BR> > 2 tables! I replaced it with a playback of [Shift][F8] and<BR> > it does the same thing. At that point things get really <BR> > screwy and if I manually start doing [shift][f8] and [f7]<BR> > eventually I will get kicked out of RBase.<BR> > <BR> > Any brainy ideas that I can try? This may blow my project<BR> > if the client isn't able to easily move through this<BR> > 'simple looking' 7-row form.<BR> > <BR> > <BR> > Karen<BR> > <BR> > <BR> > <BR> > </FONT></HTML> > --part1_d.14555d53.2c35e317_boundary-- >
