I commend Sami on her assessment, mostly because it makes perfect sense. I've encountered something similar with cursors when a table was physically re-ordered becauser the modification to the NOTE-field exceeded the padding, even though the cursor definition had an ORDER BY.
Also, Bernie, would it be possible to, say, locate a variable on the form, define it as, say ... vNoteSnipper=SGET(MyNoteField,NN,1) include a button on the form, like EDIT NOTES, that invokes an EEP that pops-up a form to edit the NOTE-field/values ... Well, I'm suggesting a bit of work in analysis/development/testing, and, as I'm just really gettin' goin' with my work for today, so my brain might not yet be in-gear, it might be appropriate to disregard everything I've said here, with the exception of the kudos to Sami. Later, Steve in Memphis ----- Original Message ----- From: "Sami Aaron" <[EMAIL PROTECTED]> To: "RBASE-L Mailing List" <[EMAIL PROTECTED]> Sent: Wednesday, December 03, 2003 8:21 AM Subject: [RBASE-L] - Re: RBW6.5+++ Form problem > Bernie - > > Try setting the NOTE_PAD value higher and do a RELOAD. When the edited size > of the note exceeds the available buffer amount R:BASE moves the record to > the bottom of the table. I can see how in a scrolling region this could > cause a hiccup. > > Sami > > > ----- Original Message ----- > From: "Bernie Corrigan" <[EMAIL PROTECTED]> > To: "RBASE-L Mailing List" <[EMAIL PROTECTED]> > Sent: Wednesday, December 03, 2003 2:30 AM > Subject: [RBASE-L] - RBW6.5+++ Form problem > > > > Hi All - > > > > I have an entry form which was performing okay > > for about six months and then started creating problems > > for the users. The form is tiered and each row contains > > a note field. Sometimes when the following conditions > > are met RBase blows up and returns the user to the > > desktop. > > > > 1) The user enters a number of rows of data with no > > NOTE field entry > > > > 2) The user enters a row of data with a NOTE field > > entry in an expanded NOTE field. When the NOTE > > field window is closed RBase blows up and kicks > > the user back to the Windows desktop. The error > > message is the usual blowup message about RBase > > having created an error that makes it impossible > > to continue running the program. > > > > The database has been completely scanned for corruption. > > There wasn't any. It has also been unloaded and rebuilt. > > > > The problem has been replicated on several machines. It > > does not occur every time the conditions for failure are > > met. > > > > Any ideas would be appreciated. > > > > TIA, > > Bernie > > > > > > > > >
