I have now spent the afternoon & early evening trying to get to the bottom of this problem.
It would appear that I can make it work as long as I do not mind having the displayed size of the form bigger than the size I want and I do not hide the background R:Base screen. This means that I have to have two caption areas at the top - one for R:Base & one for the form - which looks pretty silly. It also means that the form looks off-centre in its display area. (Yes, I can make the captions make sense or have one empty...) The strange thing is that I can get it to work most times from the R:> using RHIDE and/or NO HEADER (2 words) but if I try either command in the app file run from the desktop icon R:Base crashes almost every time. R:Syntax definitely has NOHEADER (one word) in its example for edit using! My HTML syntax help files are dated 03/03/02 - presumably still the latest? The most worrying thing here is that I cannot say positively that it fails _every_ time. The only explanation that I can offer for this is that there is some timing factor that comes into play from the icon that is bypassed from the R:>. Maybe tomorrow I'll try a modified version of David Blocker's suggestion and try a "pause for x" somewhere and see if that improves things but, right now, I need a drink! (Coffee, you understand <g>.) No, make that two! Many thanks to everybody for your help and suggestions, Regards, Alastair. ----- Original Message ----- From: "Bob Thompson" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, June 06, 2002 6:09 PM Subject: RE: Persistant System Crashes but TRACE reports no errors - Razzak's Reply > I sent the NOHEADER problem to RBTI and they replied that it must be > NO HEADER. I too experienced the disappearing form when using RHIDE > along with NOHEADER. A submittal to RDCC is being sent as the > documentation shows NOHEADER as an option. Again I was informed > it must be NO HEADER. Hopefully they will implement an error catch in > the system to give a message on NOHEADER versus the program simply > disappearing. > > By the way, the program is still running when it disappears. If you look at the > program list (Ctrl Alt Del) RBG65 will still be running. You must then END TASK > to get rid of it. > > -----Original Message----- > From: Alastair Burr [SMTP:[EMAIL PROTECTED]] > Sent: Thursday, June 06, 2002 7:25 AM > To: [EMAIL PROTECTED] > Subject: Re: Persistant System Crashes but TRACE reports no errors - Razzak's Reply > > Right, I have re-created the database from two backup files for the data > from the original db and then entered the form by hand. > > Because I could not match everything size for size and place everything in > exactly the same position the form is different from the old database one. > > As I began to test it I also began to reduce the RBGSize of the screen so > that the form filled the screen exactly. From the R:> everything was working > well until I went too far and made the RBGSize too small for the form - > crash! Now, as far as I know, this should produce scroll bars and further > testing proved that it did so there had to be something different somewhere > in what I was doing. Sometimes I used trace and sometimes I just ran the app > to test the form and it became clear that trace worked and the app didn't. > > Out of interest, it appears that you need about 5 pixels extra at the bottom > of the form and 2 or 3 to the right to get away with any scroll bars. > > Hmmm, what's odd is that trace seems to display the form with scroll bars > when the RBGSize is too small but the app when launched from the desktop > crashes. What also appears to have a further effect is whether I have the > NOHEADER option in the EDIT USING clause. If it's there it crashes. > > So I looked at my app again and the R:Syntax and found something wrong - or > so I thought: I had NO HEADER in my app - two words - but this was going > through trace quite happily. So, make it one word and - lo and behold - > trace doesn't bother to show the form anymore! > > I've spent all morning re-designing and watching this form and I need a > break now. At the moment, the new db and form is working with a simple "edit > using" command with no further additions to the command so at least I'm > better off. > > Regards, Alastair. > > > > > ----- Original Message ----- > From: "Alastair Burr" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Thursday, June 06, 2002 7:32 AM > Subject: Re: Persistant System Crashes but TRACE reports no errors - > Razzak's Reply > > > > Yes, it does, Razzak, and it has data in it. > > > > At least, I can see that is true when I run the app through trace and if I > > exit the app via a RETURN immediately prior to using the form. > > > > Hopefully, during today, I will have time to re-build the database and the > > form so that I will know that there is no corruption in the form. > > > > Thanks & regards, > > Alastair. > > > > > > > > > > ----- Original Message ----- > > From: "A. Razzak Memon" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Thursday, June 06, 2002 5:15 AM > > Subject: Re: Persistant System Crashes but TRACE reports no errors - > > Razzak's Reply > > > > > > > > > > At 11:29 AM 6/5/2002 +0100, Alastair Burr wrote: > > > > > > >However, there are _no_ while loops in the app. All it does is gather > > some > > > >info from one database and create a temp table with that data in the > > driving > > > >database for use in a form for display purposes. The form does not get > > > >updated as it has a number of buttons which run other apps. It has only > > > >started crashing since adding the temp table with the displayed data to > > the > > > >form. > > > > > > Alastair, > > > > > > 01. Before you use the form, make sure that associated TEMP table really > > > exist. > > > > > > 02. TEMPorary TABLE(s) disappear when the database is DISConnected > > > or CONNected again. > > > > > > Hope that helps! > > > > > > Very Best Regards, > > > > > > Razzak. > > > > > > > > > > > > ================================================ > > > 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/ ================================================ 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/
