Dear Craig,
I agree. My vote would be for all developers to have read access to all
posted bugs with the ability to confirm that they could duplicate the
bug. 6 out of my last 11 posted bugs RBTI have been unable to duplicate.
At 11:28 10/05/01 -0400, you wrote:
>Is there anywhere I can get a list of current bugs in the current (not
>beta) build? Looked at rbase site, developers corner, documentation
>included with software, nothing.
>
>Probably would save me weeks right now as I have already wasted a week on
>the enter using..for 1 row problem that I requested help for earlier in
>the week (now I'm sure it's a bug - I can't get it to add more than 1 row
>to subsequent tables as advertised, even using the concomp db.
Just a thought on a workaround, why not insert a datum into the parent
table then use ENTER USING FormName? You would need to set the table
properties for the parent table in the form to disallow entry of new rows
but it would solve the problem of inability to add new rows to child tables.
You will notice that there are various differences in the way the form
behaves with EDIT vs ENTER but as I understand it your parent table has
only one row on the form so it _should_ not pose a problem.
> Since nobody responded to my original post, I'm pretty sure I'm not
> missing anything...) also, thankfully I saw on this list that others
> noticed eep only commands (saverow, nextrow, etc...) also don't work in
> RBWin, that one had me befuddled there for a while too. I'm a month into
> converting a very large system written in 4.5+ and would hate to scrap
> the whole thing - but I can't keep running into brick walls.
Here's my write-up on the major show stopper for me in 6.5+.
Briefly it involves using #DUP in a form with SAVEROW in an eep part way
through the row.
If you do not use that procedure then skip this.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~``
I have a single table form with a scrolling region that was working fine in
6.1. The first 17 fields in the region are variables, the remainder are
columns. The 1st, 2nd, 4th, 5th then 7th through to 17th fields are set
with #DUP. The first row does what it should. When I press [Enter] and
move the cursor to the next row the fields that are supposed to be
duplicated are and those that are not aren't. So far so good.
But when I press enter on fields one and two to move into field three the
value 1 appears when it should not. There is no field level eep on entry
to field 3.
Furthermore when I move to a field containing an eep (field 10) which
recalcs the variables the value in field one (which was 1) is lost and the
field is now blank. This is the eep:
$COMMAND
CalcBrk
SET VAR vTime TIME = .vStartTime
RUN Time2Dbl IN GlobBlok.apx
SET VAR vST DOUBLE = .vTimeDbl
SET VAR vTime TIME = .vEndTime
RUN Time2Dbl IN GlobBlok.apx
SET VAR vET DOUBLE = .vTimeDbl
IF vET < .vST THEN
SET VAR vGH DOUBLE = ((24 - .vST) + .vET)
ELSE
SET VAR vGH DOUBLE = (.vET - .vST)
ENDIF
IF vGH >= 5.0 THEN
SET VAR vBreakTime TIME = 0:30
ELSE
SET VAR vBreakTime TIME = 0:00
ENDIF
RECALC VARIABLES
RETURN
When I press [Shift]+[Tab] to go back to a prior field focus moves to a
copy of Windows Explorer I have open.
When I press [Tab] to go forward a field the focus switches to another copy
of Windows Explorer. (I have two open to transfer files from the Desktop
to Laptop.)
If I click in Field 1 and enter the value 1 and move forward by pressing
[Enter] the second time through the row the first field does not lose it's
value. The row has been saved by an eep by this time.
Warmest regards,
Tom Grimshaw
coy: Just For You Software
tel: 61 (0)2 9552 3311
fax: 61 (0)2 9566 2164
email: [EMAIL PROTECTED]
mobile: 0414 675 903
street: 3/66 Wentworth Park Rd Glebe NSW 2037
post: PO Box 470 Glebe NSW 2037 Australia
temp web site: 210.9.46.35
_/_/_/_/_/_/_/_/ _/_/_/_/_/_/ _/ _/ _/_/_/_/_/
_/ _/ _/ _/ _/
_/ _/ _/ _/ _/
_/ _/_/_/_/ _/ _/_/_/_/_/
_/ _/ _/ _/
_/ _/ _/ _/ _/
_/ _/ _/ _/_/_/_/_/
