Steven,

I'd have to agree with Sami here... it seems I've even experienced 
what you're going through, but couldn't say for sure. As an aid, use 
RStyle to check your code, it'll catch 98% of what you might screw 
up and makes your code pretty in the process :) .

Ben Petersen


On 23 Oct 2002, at 15:31, Steven Hoggan wrote:

> Sami,
> 
> Thanks for the reply.  I'm afraid my original email was poorly
> phrased. When I said I used other applications, I actually meant Word,
> Excel, Exchange, etc.
> 
> I'm happy to check my coding, but I wouldn't have thought poor coding
> would be to blame for the *crash* when pressing a key while sitting at
> the R> (having used other non-Rbase applications in the meantime).
> 
> I'll be checking out my code, anyway.
> 
> Thanks for your time and input.
> 
> Regards
> 
> Steven
> 
> > ----------
> > From:       Sami Aaron[SMTP:[EMAIL PROTECTED]]
> > Reply To:   [EMAIL PROTECTED]
> > Sent:       23 October 2002 15:15
> > To:         [EMAIL PROTECTED]
> > Subject:    Re: RBW 6.5++ /Win2K Pro
> > 
> > Steve -
> > 
> > In my experience, this error is usually caused by programmer error -
> > i.e.:
> > 
> > unmatched quotes,
> > unmatched parens.
> > a variable being cleared before it should have been,
> > a variable being typed differently than it should have been
> > a reference to a variable that has not been defined
> > 
> > Since it's sporadic and since you are running different apps, I'd
> > guess that one of them is either clearing a variable that it
> > shouldn't, or that it's using the same variable name in different
> > apps with different data types and not clearing between apps.
> > 
> > I'd check out each of the apps for variable names and when they are
> > cleared., Then I'd work in the tracer with MESSAGES, ERROR MESSAGES,
> > and DEBUG on all day and see what error messages you get.
> > 
> > Sami
> > 
> > -----------------------------------------------------------
> > Sami Aaron
> > Software Management Specialists
> > 19312 W 63rd Terr
> > Shawnee KS  66218
> > 913-915-1971
> > http://www.softwaremgmt.com
> > 
> > ----- Original Message -----
> > From: "Steven Hoggan" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Wednesday, October 23, 2002 7:01 AM
> > Subject: RBW 6.5++ /Win2K Pro
> > 
> > 
> > > Hello,
> > >
> > > This has got to be such a straightforward problem that I'm sure
> > > someone
> > out
> > > there will be able to help immediately.  I'm afraid my ISP is
> > > having
> > major
> > > Denial of Service attcks at the moment, so I can't access the
> > > Internet
> > to
> > > research this myself.
> > >
> > > So,
> > >
> > >
> > > RBW6.5++  Build 1.850xRT03 running under W2K Pro, SP1.
> > > P4, 1.6GHz, 256MB RAM, 20GB HDD, swap file size min 384MB.
> > >
> > > I am developing a one-form application that (generally) behaves
> > > fine. On exiting the application, I sit at the R> and then fire
> > > away using other applications.  Sometime, not always, when I
> > > return to Rbase and press a
> > key
> > > I get the following message.
> > >
> > >
> > --------------------------------------------------------------------
> > ------ --
> > > -----------------
> > > RBG65.exe has generated errors and will be closed by Windows. You
> > > will need to restart the program
> > >
> > > An error log is being generated.
> > >
> > --------------------------------------------------------------------
> > ------ --
> > > ----------------
> > >
> > > I say the application generally works fine because 90% of the time
> > > it
> > does.
> > > Some times, however, the above message is generated mid-program.
> > >
> > > I'll not bother you with details of the application, since I'm
> > sure/hoping
> > > this is fundamentally a resource problem between Rbase and W2K. 
> > > If
> > details
> > > are needed, however, I can gladly supply them
> > >
> > > I am sure there are a number of things to try (in the absence of
> > > an
> > Internet
> > > connection for the moment, I can't even research them), but if
> > > someone
> > could
> > > identify *one* specific thing (perhaps a memory setting/whatever)
> > > to
> > set/try
> > > I'm sure I could kill the vast majority of crashes stone-dead.
> > >
> > > Thanks for all and any replies.
> > >
> > > Steven
> > >
> > >
> > >
> > >
> > >
> > > Privacy & Confidentiality Notice
> > > ----------------------
> > >
> > > This message and any attachments thereto is confidential and
> > > intended
> > solely
> > > for the person to whom it is addressed.  It may contain privileged
> > > and confidential information.  If you are not the intended
> > > recipient you
> > must
> > > not read, copy, distribute, discuss or take any action in reliance
> > > on
> > it.
> > > If you have received this information in error, please notify us
> > > as soon
> > as
> > > possible on the telephone number shown.  Thank you.  Fitzpatricks.
> > >
> > > Tel:  +44 (0)141 306 9000
> > > Fax:  +44 (0)141 306 9090
> > > Web:  www.fitzpatricks.co.uk
> > > ================================================
> > > 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/
> > 
> > 
> > 
> > 
> > 
> > 
> Privacy & Confidentiality Notice
> ----------------------
> 
> This message and any attachments thereto is confidential and intended
> solely for the person to whom it is addressed.  It may contain
> privileged and confidential information.  If you are not the intended
> recipient you must not read, copy, distribute, discuss or take any
> action in reliance on it. If you have received this information in
> error, please notify us as soon as possible on the telephone number
> shown.  Thank you.  Fitzpatricks. 
> 
> Tel:  +44 (0)141 306 9000
> Fax:  +44 (0)141 306 9090
> Web:  www.fitzpatricks.co.uk
> ================================================
> 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/

Reply via email to