> "that's just the way it is sometimes" exploitation<
Sorry, I'm not sure how "explanation" became "expoitation"...
(may explain a few things <g>)
Ben Petersen
On 2 Aug 2001, at 11:57, Ben Petersen wrote:
> Sami,
>
> My experience is more like JM's. Distributing the same app with
> the same RB run-time might generate inexplicable errors on
> something like 1 in 5 or so sites. My experience is different in that
> it's not related to buttons or eeps, necessarily, but just in the
> general code.
>
> It happens rarely, and is not reproducible other than on the client's
> computer (downloading their data to my system and running the
> app showed no problems). _Rearranging_ code (moving the block
> where things break up or down a few lines) has solved the problem
> twice. I'm still working on a solution for the third such incident.
>
> It's rare enough to not be a major worry, but has occurred often
> enough to make me sit up and take notice. One list contributor
> calmed me with a "that's just the way it is sometimes" exploitation
> <g>, which saved me from further bloodying my forehead on the
> wall next to my desk.
>
> Ben Petersen
> On 2 Aug 2001, at 9:29, Sami Aaron wrote:
>
> > J.M. -
> >
> > In my experience, in almost EVERY instance of the "Fatal error" message, I
> > have found that the problem is MY programming! Either a variable that
> > should be in memory isn't, or a variable was pre-defined with a different
> > datatype than it expects now, or there is an unbalanced set of quotes or
> > parentheses, or something else that earlier versions of R:BASE were more apt
> > to either forgive or ignore.
> >
> > Since the problem is sporadic, I would be sure to clear all unnecessary
> > variables before and after using the form and the eep. I often name
> > variables called in an eep with a different naming convention than other
> > application variables and form variables so they can be cleared easily after
> > using, and they won't conflict with other existing variables.
> >
> > Good luck!
> > Sami
> >
> > Sami Aaron
> > Software Management Specialists
> > 13214 W. 62nd Terr, #139
> > Shawnee KS 66216
> > 913-915-1971
> > http://www.softwaremgmt.com
> >
> > ----- Original Message -----
> > From: "J.M. GRATIAS" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Thursday, August 02, 2001 6:31 AM
> > Subject: RE: Merging forms into one database - Razzak's Reply
> >
> >
> > >
> > > >>
> > > in the application that we are developing we have utilized many push
> > > buttons
> > > to take us to different forms and screens, as the program returns to the
> > > originating point (after the push button eep has executed) we are getting
> > > an
> > > application error (fatal) "DR WATSON type" which shuts down the program
> > and
> > > returns us to the desktop. Any ideas?
> > > <<
> > >
> > >
> > > I have the same problem ....
> > > Hapen only on some hardware, and always with NT 4.0 SP 4 or 5, RBW 6.1a
> > and
> > > 6.5 ++
> > >
> > > Last time was about 2 weeks ago. I sent Dr WATSON debug file to RDCC.
> > >
> > > You could try 2 things :
> > >
> > > Change display setting : 64/32 bytes colors to 16 bytes or 256 colors ....
> > > Increase virtual memory.
> > >
> > > Sometimes it help ...
> > >
> > > This a very old problem (I reported it about 2 yaers ago) that have never
> > > been fixed because nobody have never been able to duplicate it ....
> > >
> > > Hope this help,
> > >
> > > J.M. GRATIAS, Logimatique
> > >
> > >
> > >
> >
> >
>
>
>
