Hi Tom, 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 - although I am about to. Indeed, if I hadn't been in the middle of converting my main (and biggest) database to Windows I would have got involved with testing but I didn't want to have too many changes going on at once (I've been there and done that and, for once, learned from my experiences).
Thanks for the suggestion for the buttons - I'll try that and see how it works but I can't believe that Razzak &Co haven't squashed any bugs that are known about! Regards, Alastair. ----- Original Message ----- From: "Tom Grimshaw" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, January 01, 2002 7:26 PM Subject: Re: Creating Windows forms > G'day Alastair, > > A Happy New Year back to you. > > I can address the last one! > > Set the first table (of the two tables with which you > wish to associate the two buttons) as the current table. > Create a button for the Next Table function with only a > single space as the button text. > Set the next table as the current table. > Create a button for the Next Table function with only a > single space as the button text and position this one > exactly over the top of the first one. > Create a text field containing [Next Table] and position > it above or below the overlayed buttons. > Draw a box around the two overlayed buttons and text. > Voila! Your workaround. > > What version are you using? > > The integrity of the commands you are trying to use were > severely compromised in the last MicroRIM release but I > have not yet had the chance to see if the R:Team squashed > that bug in the latest patch. > > At 07:07 PM 01/01/2002 +0000, you wrote: > >However, I am having a few teething troubles with EEP commands to go to > >the next table and row: > > > >For example, if I use the menu bar Forms option or the Function Keys I > >have no problems but if I create an EEP on a Text Button to go from the > >second of three tables to the first table of the next driving row I get an > >"Out of memory" error message. > > > >My EEP currently is this: > > > >PREVTAB > >NEXTROW > >RETURN > > > >I have tried: > > > >SAVEROW > >NEXTTAB > >NEXTTAB > >NEXTROW > >RETURN > > > >and a few variations on things in-between but always get the out of memory > >error. > > > >I can click on the message and then go to the next row "manually" without > >any further problem. Buttons to do a single task - Next Row or Next Table > >work fine. > > > >I can't think why it would be relevant but my first two tables are on one > >page and the third on the second page - I'm used to Paging Down from Dos > >and haven't found a need to try the Windows Screen Areas instead. > > > >Does anybody have any advice, please? > > > >Also, if I have a button associated with the first table for Next Table it > >becomes greyed out when I get to the next table and I need another Next > >Table button associated with the second table to from there to the third > >table. I can understand why this happens but does anybody have a way of > >combining the two buttons or displaying only the "current" one? > > 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 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
