Just to close this thread: As you all knew it would the in-line patch solved the memory error message problem - thank you to everyone at RBTI.
The button text problem has been worked around with Tom Grimshaw's help - although I have taken his idea and changed it. What I have done is this: Create a button for each table with the text "Go!" and a text box with the relevant text on it. I have made the text box big enough for the two "Go!" buttons to sit on either side of the text. ====================== || Go! || Descriptive Text || Go!|| ====================== As only one button shows its text at any time this looks reasonable and it is clear what to click on. Thanks, Tom, please feel free to make use of this and/or improve on it if you like. Regards, Alastair. ----- Original Message ----- From: "Alastair Burr" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, January 02, 2002 7:13 AM Subject: Re: Creating Windows forms - Razzak's Reply > Hello Razzak, > > As I outlined in my reply to Tom I had not upgraded to the latest patch or > got involved in testing the betas because I was - still am - in the middle > of converting my main database from Dos to Windows and I didn't/don't want > to have something else in a beta version changing at the same time as I get > to grips with changes in the released version. > > As to taking the released version of the patch it was only made available > less than 48 hours ago and I tried to download it but found that I didn't > have an upgrade code - although I am (fairly) sure that I have kept > everything that has been sent to me. Having now got that code - on New > Year's Day, thank you and well done! - from Tech Support I am about to > download it. I am also much more happy to apply a "released" patch that use > a beta one whilst I am in the middle of my own changes. > > That being said, the problem appeared well before Christmas and I have spent > days trying to resolve it myself - assuming that it was me doing something > wrong with unfamiliar techniques in Windows' forms. I had no reason to > assume it was a bug until I had tested every possibility that I could think > of and - even then, when I asked this list for help - I still presumed that > it was me doing something stupid. > > Of course, I am delighted that the patch will resolve this problem and any > others that I have had. And, as I also said to Tom, I am _definitely_ having > fun with R:Base for Windows - it can do so much more than the Dos version > with its graphical interface that was just impossible in the old 80x25 > character format. > > Regards, > Alastair. > > > ----- Original Message ----- > From: "A. Razzak Memon" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Wednesday, January 02, 2002 2:15 AM > Subject: Re: Creating Windows forms - Razzak's Reply > > > > > > At 08:55 PM 1/1/2002 -0000, Alastair Burr wrote: > > > > >... I'm using RBW6.5++ but without the latest patch - I've > > >been too busy enjoying myself (and not just with R:Base!!) > > >to upgrade yet - ... > > > > >... but I can't believe that Razzak & Co haven't squashed > > >any bugs that are known about! > > > > > > Alastair, > > > > I guess it would have been perfectly fair if you would have > > taken the time to try the latest patch to see if the issues > > still remain in the CURRENT version of The Glorious R:BASE > > 2000 (version 6.5++), Build:1.850xRT03. > > > > Just for the record, EVERY submitted and replicable bug has > > been SQUASHED by The Dream Team! > > > > We have worked very hard to bring out the BEST of R:BASE, > > but, if for any reason, someone does not have the time to > > test before posting or at least confirming, then, there is > > nothing we can do. > > > > Please read RBW65PP1.TXT for more details and I'm sure you > > will be impressed. > > > > Keep in mind that if you have some issues, the best way to > > have them taken care of is to submit a request on R:DCC, > > along with a sample database, command files to fully explain > > the bug and help our dedicated R:Team to replicate it. Once > > it is replicable using the CURRENT version of R:BASE, then > > consider it done in the next possible patch or release. > > That's how we do it right. > > > > All we can do is to keep working hard and do what we are > > good at. > > > > The rest is history. > > > > May you all enjoy the hard work of The Dream Team and the > > tireless efforts of the beta testers. > > > > The BEST is yet to come. > > > > Very Best Regards, > > > > Razzak. > > > > > > ===================================-============================ > > R:BASE Developers's Conference: http://www.rbase.com/conference > > Official R:BASE List Server: mailto:[EMAIL PROTECTED] > > RBTI Events/Training: http://www.rbase2000.com/events > > R:DCC Members: http://www.rbase2000.com/rdcc > > ================================================================ > > R:BASE, Oterro & R:Tango are registered trademarks of RBTI. > > ==================================-============================= > > > > ================================================ > > 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 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 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
