Hi Ian, nice to hear from you again. Actually, there is no need for me to use 3 tables as all I am doing is amending data in either of the first two and using the third for reference. In this particular case the third table is a view made up of specific rows from two other tables - and, therefore, not editable but I have a dummy variable for the cursor to land in and to scroll through the rows.
I guess that I could make a view containing all the tables but I've usually had problems updating views in the past and a temporary table would be quite big - but worth thinking about, all the same. Using an EEP to update the table(s) might be the way to go here. That said, if R:Base is designed to use forms with up to 5 tables/views then there should be little problem and, as Razzak has pointed out, the patched version resolves this particular problem. Unfortunately, I've not had time to download the patch and apply it yet but I hope to do it today. Many thanks for your help - I'll ring if I need to! Regards, Alastair. ----- Original Message ----- From: "Ian Stone" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, January 02, 2002 8:53 PM Subject: Re: Creating Windows forms > Hi Alastair > > I've learnt the hard way with trying to build windows apps the way we did > them in DOS. > > I believe in keeping it simple, ask your self if you need to have 3 linked > tables on one form? You can make it look like 3 or more tables to the user > but by loading the data you need into a temporary table or view you can be > more flexible and often get a speed enhancement though this may be look > Irish in the first instance. Also the use of dynamic QUIT TO(s) can > enhance the look, stability and feel of your app, this will eliminate all > the NEXT/PREVIOUS stuff. If you want more information give me a bell > (01584 876698). > > Ian > > The Wild West (Just in England) UK > > > AAt 19:07 01/01/2002 +0000, you wrote: > >Hi all - a happy New Year to all of you. > > > >Over the last few days I have begun to create forms that are beginning to be > >worthy of R:Base for Windows and make use of many features that simply were > >not possible in Dos environment. Whilst I could probably could have done the > >database tasks in Dos it stood no chance of displaying as many fields as I > >now can. > > > >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? > > > > > >Thanks in advance > >Regards, Alastair. > > > > > > > > > > > >---------------------------------- > >A D B Burr, > >St. Albans, UK. > >---------------------------------- > >[EMAIL PROTECTED] > >---------------------------------- > > > >================================================ > >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
