Bernie, I have a form that has a scrolling region as the second table.
I kept fighting a problem like yours using variables. I finally bit the bullet and added basically some navigator buttons for the scrolling region. I put non-editable DB-Edits in the scrolling region. The add would either use a dialog box or a choose to query the user for the information and validate it. Then I use the ever wonderful PROPERTY command to fill in all the DB-Edits with the proper information and use the TABLE PROPERTY command to add/delete/next/whatever the scrolling region. Works pretty good. Only took about an hour to implement and I don't have to figure out the variables. Considering that I fought it for a couple of days the fix was simple. Guess I'm hard-headed and old ways die hard. You can tell a Dane but you can't tell him much. Have a good week-end. Jan ----- Original Message ----- From: "Bernard Lis" <[EMAIL PROTECTED]> To: "RBG7-L Mailing List" <[email protected]> Sent: Friday, March 18, 2005 12:57 PM Subject: [RBG7-L] - strange 2 table form behavior > I hope someone can turn the light bulb on for me. > Form has 2nd table as region. > After entering data in last col of main table, the cursor goes into the 2nd > object in the region, not the first. Why? > The tab order in the region shows the first object as first. > The first object is a variable, the rest are columns. Should that make any > difference? > When the first row in region is completed, the cursor goes into the correct > first object in the 2nd row. > > Also, after entering the 2nd row and going into the 3rd row, the variable in > the first row displays the value of the 2nd row. That shouldn't happen, > should it? > > Bernie Lis > >
