Thanks, Steve, I'll try that - I've done everything else but minimise it first, I think!!
Regards, Alastair. ----- Original Message ----- From: "J. Stephen Wills" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, March 19, 2002 2:48 PM Subject: RE: Forms.Region.Tiered.NEXTROW.INTENSITY => Navigation Problem > The behavior you mention seeing in BROWSE ... mode, a data-grid > presentation, I think I've seen also. I see it when I expand the BROWSE > window to full-screen. When the window redraws, I see only the records > which were originally presented in the smaller window, with the remainder of > the window appearing as empty/white space. By happenstance, trial & error, > what-have-you, I've found a workaround. When I get those "empty" spaces, I > minimize the window, then I maximize/restore. This apparently forces a both > a refresh and a redraw of the window. Apparently, only a redraw, absent > some sort of refresh, is part-and-parcel to this issue. > > Maybe this'll help - I hope so, > Steve in Memphis > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On > > Behalf Of Alastair Burr > > Sent: Monday, March 18, 2002 4:56 PM > > To: [EMAIL PROTECTED] > > Subject: Re: Forms.Region.Tiered.NEXTROW.INTENSITY => Navigation Problem > > > > > > Hi Tom, > > > > I can confirm that I've seen this too - I just assumed it was me getting > > tired or something as nobody else seemed to have mentioned it. > > > > The other thing I get - and I might as well mention now as it might be > > related - is that if I press [Ctrl]/[End] to get to the last row the > > browser/editor appears to contains empty rows. It seems to depend > > on whether > > I maximise the screen before doing anything else - sorting, > > scrolling, etc. > > I have to quit the browser and re-enter to get the data in the rows back > > again. > > > > Regards, Alastair. > > > > > > > > ----- Original Message ----- > > From: "Tom Grimshaw" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Tuesday, March 19, 2002 3:34 PM > > Subject: Re: Forms.Region.Tiered.NEXTROW.INTENSITY => Navigation Problem > > > > > > > G'day, > > > > > > I don't know if this is related or not ('cos it's in the > > > data browser, not in a form) but I have observed a problem > > > while browsing records in the table views that smacks of > > > similarity. > > > > > > Yesterday I did a PROJECT of a sub-set of records from my > > > C_PostCodes table, add a column to the new table and > > > started browsing the records, occasionally adding a new > > > record to the table. > > > > > > Several times I would resequence the rows in the table to > > > view the data in a different order. At one point I > > > needed to be at the bottom of the table so I pressed and > > > kept depressed the PgDn button on the keyboard. > > > > > > As I did this for slightly longer than the time necessary > > > for the cursor to hit the bottom what happened was that > > > R:BASE appeared to duplicate the last row of data. > > > > > > Because I had added this particular record I did not at > > > first realise that it was, in fact, a duplicate. I > > > wondered whether or not I had added a postcode that was > > > already present. > > > > > > Navigation seemed to confirm that it was a valid row which > > > threw me. Normally if I have problems of this nature in > > > the browser (such as I did on another occasion yesterday > > > when trying to paste the value from a PK column in the > > > C_PostCodes table into the projected table) when I move up > > > from the row where the error message occurred the row > > > below the error message will be duplicated in the > > > error message row. And vice versa, if I move down the row > > > above the error message will appear also in the error > > > message row. > > > > > > Back to the other bug, I could move from the last to the > > > second last row of data, from the second last to the last > > > and higher and the display remained valid. > > > > > > So I deleted the "duplicate" row. Only it _wasn't_ a > > > duplicate. > > > > > > This happened on more than one occasion so, for me anyway, > > > it is replicatable. > > > > > > Before I submit it as a bug to RDCC, because often times > > > they cannot duplicate what I experience (got something to > > > do with the water exiting the other way around in the > > > Northern Hemisphere :-)) has anyone else any data on this? > > > > > > At 11:02 18/03/02 -0600, you wrote: > > > >Okay, I've created several forms w/tiered regions and tested this > > w/similar > > > >results. I say similar because I just ain't gonna' take the time to > > isolate > > > >this behavior beyond what I've done so far, unless RBTI wants > > to hire me > > as > > > >a S/W Q/A Manager, and that's not a hint, because I already have a job > > and > > > >I'm tryin' to spend my time doing that job, using RBase as a > > tool to aid > > in > > > >the performance of that job. > > > > > > Warmest regards, > > > > > > > > > Tom Grimshaw > > > coy: Just For You Software > > > tel: 612 9552 3311 > > > fax: 612 9566 2164 > > > mobile: 0414 675 903 > > > > > > post: PO Box 470 Glebe NSW 2037 Australia > > > street: 3/66 Wentworth Park Rd Glebe NSW 2037 > > > > > > email: [EMAIL PROTECTED] > > > web: www.just4usoftware.com.au > > > > > > This email and any files transmitted with it are confidential to the > > > intended recipient and may be privileged. If you have received > > this email > > > inadvertently or you are not the intended recipient, you may not > > > disseminate, distribute, copy or in any way rely on it. Further, you > > should > > > notify the sender immediately and delete the email from your computer. > > > Whilst we have taken precautions to alert us to the presence of computer > > > viruses, we cannot guarantee that this email and any files transmitted > > with > > > it are free from such viruses. > > > > > > ================================================ > > > TO SEE MESSAGE POSTING GUIDELINES: > > > Send a plain text email to [EMAIL PROTECTED] > > > In the message body, put just two words: INTRO rbase-l > > > ================================================ > > > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > > > In the message body, put just two words: UNSUBSCRIBE rbase-l > > > ================================================ > > > TO SEARCH ARCHIVES: > > > http://www.mail-archive.com/rbase-l%40sonetmail.com/ > > > > ================================================ > > TO SEE MESSAGE POSTING GUIDELINES: > > Send a plain text email to [EMAIL PROTECTED] > > In the message body, put just two words: INTRO rbase-l > > ================================================ > > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > > In the message body, put just two words: UNSUBSCRIBE rbase-l > > ================================================ > > TO SEARCH ARCHIVES: > > http://www.mail-archive.com/rbase-l%40sonetmail.com/ > > > > ================================================ > TO SEE MESSAGE POSTING GUIDELINES: > Send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: INTRO rbase-l > ================================================ > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: UNSUBSCRIBE rbase-l > ================================================ > TO SEARCH ARCHIVES: > http://www.mail-archive.com/rbase-l%40sonetmail.com/ ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
