I'm still not able to resolve the problem of getting an automatic "refresh" of the scrolling regions in the lower tables of my form.
As nobody has responded to my original question on this particular part of the problem let me ask it in a different way: If I use an "On Row Entry" EEP for the driving table then the first scrolling region displays correctly sized on running the form. However, moving to subsequent rows in the driving table doesn't update the size via the EEP. If I move the EEP to the displayed variable's "On Entry" EEP when I click on the variable the display is updated. What is stranger is that for the second and third scrolling regions their display is updated as I want when clicking on any row from the preceding scrolling region(s) with the EEP placed as a table "On Row Entry" one. What I'm trying to program is for the first scrolling region to resize based on changing rows in the driving table and the subsequent scrolling regions to change size either based on the first row or the currently selected row. More logically, I think, is for all the scrolling regions to return to the first row when the driving table row is changed. However, no combination of skip and property commands that I've tried seems to move the selected row to the first and run the "On Row Entry" for its driving table. The re-sizing works fine - and looks great - but I want to avoid the mouse clicks needed to update the displays that I seem to require at the moment to activate the EEP. Has anybody any ideas what I'm doing wrong? For example: The driving table is on the row "Fred". There are 2 rows associated with Fred in the first s/r so that needs 2 rows displayed. For the first of those rows there are 3 rows in the second s/r and for the second row there are 10 rows in the second s/r. The second s/r needs to re-size to either 2 rows or 10 rows depending on which row in the first s/r is selected. The third s/r needs to re-size depending on the number of rows associated with the current row in s/r number 2. When moving to the row "Joe" there might be 10 rows to display for the first s/r and the relevant numbers of rows for the subsequent s/r's depending on which row is selected. It's this change that I'm trying to get to work with the first row of each of the 3 s/r's selected or active without having to click anywhere. By the way, concerning the "Invalid Text" problem, I attempted using an additional column and using SRPL to replace any single quotes in my views but this slowed the response dramatically. If I had thought about it first I might have realised that the view had to calculate all the SRPLs before the links could be made. I now use temp tables and insert the basic data with a computed column to do the SRPL. Naturally, this is very fast and solves the "Invalid Text" error. Thanks again, Albert. Regards, Alastair. ----- Original Message ----- From: "Alastair Burr" <[EMAIL PROTECTED]> To: "RBG7-L Mailing List" <[email protected]> Sent: Monday, March 07, 2005 9:12 PM Subject: [RBG7-L] - Re: Dynamic size Scrolling Regions: a little local difficulty > Thanks, Albert, it's strange that I haven't noticed it before but I've > always tried to link on IdNums of some sort so perhaps I've just been > fortunate. > > Happily, though, the form is based on views so, with luck, I can add a > computed column that does a trick or two, link on those and rename the other > links. > > Regards, > Alastair. > > > ----- Original Message ----- > From: "Albert Berry" <[EMAIL PROTECTED]> > To: "RBG7-L Mailing List" <[email protected]> > Sent: Monday, March 07, 2005 6:26 PM > Subject: [RBG7-L] - Re: Dynamic size Scrolling Regions: a little local > difficulty > > > > Alastair, I have some databases that use double quotes because of this > problem with single quotes > > in name fields such as "O'Brien". You have to somehow double up the quote > in the linking field so > > it takes the quote as a literal character rather than a quote, which > terminates the text field > > prematurely. > > > > Yes, the SQL standard is single quotes, but No, it's not the best thing > going in some cases. The > > hoops jumped through to get fields with apostrophes in them to work can be > eliminated very simply > > by using double quotes. > > > > SET FLAME_PROOF_UNDERWEAR ON > > > > > > --- Alastair Burr <[EMAIL PROTECTED]> wrote: > > > I have a form based on 4 tables. The driving table simply returns a > looked-up name with the > > > other 3 tables each returning a scrolling region based on the preceding > table. > > > > > > I have been attempting to dynamically size the scrolling regions to > return the number of rows > > > found for each table. > > > > > > I have the maths working fine and each one works individually but I have > two things which I > > > haven't found a solution for yet: > > > > > > Firstly, I seem to have to click into each region to get it to adjust > its size; and > > > secondly: there is a lot of flashing of the screen as each one is > changed. > > > > > > I've tried every combination of Set_Focus and Skip To and table > properties for First, Refresh, > > > Recalc, etc that I can think of but not found the missing ingredient. > > > > > > One other thing that is related to scrolling regions but not > particularly to this form - as far > > > as I know - is that I am getting some "Invalid Text Value" error > messages - apparently - > > > whenever the linking (text) columns contain a single quote (as an > apostrophe). Is this something > > > that needs to be reported as a bug (upgrade #80/RC2)? > > > > > > Thanks & regards, > > > Alastair. > > > > > > ---------------------------------- > > > A D B Burr, > > > St. Albans, UK. > > > ---------------------------------- > > > [EMAIL PROTECTED] > > > ---------------------------------- > > > > Albert Berry > > Management Consultant > > RR2 - 1252 Ponderosa Drive > > Sparwood BC, V0B 2G2 > > Canada > > (250) 425-5806 > > (250) 425-7259 > > (708) 575-3952 (fax) > > [EMAIL PROTECTED] > > >
