Razzak, I have examined and borrowed from the fabulous SalesOrder form many times especially the scrolling region. I was doing what Bob described, putting a variable label on the scrolling region. It appeared to work except for the anomaly reported. I also recently tried to put a Db Combo box and a DB Lookup ListBox on a scrolling region and I got the message: "You cannot insert this control into a scrolling region!". However, I successfully put a DBUserdefined combo and listbox on a scrolling region and although the objects don't work - they're gone after you save the form and re-enter - there is no error message!?!? My pet peeve would be that since these objects won't work (and that applies to variable labels and whatever else I haven't tried that won't work), they should generate an error message so that the user is aware that they cannot be used. I, for one, can't memorize which objects will work and those which will not! It's hard enough (at my age) to remember what I had for breakfast! <g>
So, my enhancement request is: please add error messages to help guide us to use only objects that work... Claudine :) -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of A. Razzak Memon Sent: Sunday, July 18, 2004 10:17 AM To: RBG7-L Mailing List Subject: [RBG7-L] - Re: Scrolling Region Oddity At 04:41 PM 7/16/2004 -0400, Bob Castanaro wrote: >I have been trying to easily create a data entry form with a >scrolling region based on a table (enter formname). If I have >DBEdits only in the region, the rows show up and it properly >scrolls down to the next row after data has been entered in >the last field in the row. I can see all the rows I have >entered. >If I have a lookup variable located in the region, it shows >the lookup, still saves the row, but all the data disappears >and it starts all over in the first field in the first row. >Is this normal behavior for this, or am I forgetting to do >something to make this work? Bob Castanaro and Claudine Robbins: Running R:BASE Your Way! (Part 5 through 11) includes a "SalesOrder" form with "Scrolling Region" having DBEdit as well as Variable Edit (lookup) controls. Do you see the same oddity (as you have described above) using the SalesOrder form? To test the same scenario: 01. Start RBG7.1 (Update 76 or higher) 02. Switch the default working directory to: C:\RBTI\RBG7\Samples\Databases\RRBYW8 03. Database Explorer > Command Files > RRBYW8.DAT > Run 04. RRBYW8 Main Menu > Sales > New Sales Order(s) Select the appropriate information for the "Sales Header" (Sales Rep, Bill To, Ship To, etc.) 05. For Line Item and Details ... click on "Line No." . Notice the automated number for the first line item . Double-click on Model and select the appropriate Product (Notice the look-ups for Product Name, Location, List Price) . Enter Discount(%) if necessary . Enter Qty and press [Enter] (Notice the calculated "Extended Price" as well as the position of the cursor on the next line with automated Line No.) 06. Repeat step 05 for at least four or five times Do you see any oddity there? Does the data disappear and does it start all over in the first field? To understand the scenario: 01. Start RBG7.1 (Update 76 or higher) 02. Switch the default working directory to: C:\RBTI\RBG7\Samples\Databases\RRBYW8 03. Database Explorer > Command Files > GlobalVars > Run Database Explorer > Command Files > TempTbls > Run 04. Database Explorer > Forms > Sales Order > Design . Take a look at all DB Edit and Variable Edit controls including the properties of all DB Edit and Variable Edit controls . Also, take a look at Scrolling Region Properties: (Table Name and Tiers) Hope that helps you understand! Very Best R:egards, Razzak.
