Well said Mike.
Anyone that has moved 5000/2.11/3.0 code to the present is well aware of
this exact issue. As RBase has been improved ("Tightened Up"), many of the
old sins are not forgiven in the current version (look at how forgiving
reports were in the dos version compared to RBwin). I_am_not_aware of a
"single replicable" negative anomoly (Bug?) that has been sent to the
Development Staff that has not been acted upon and to quote Razaak
"Quashed".
Further, I am reminded of a time, in the not distant past, when this forum
was used for other than its' stated purpose, that of casting aspersions and
how it seemed to make everyone, well, Less. So I would not want this thread
to get legs. I have a great deal of respect for people on both sides of
this issue and I would like to see this worked out through the proper
channels.
With that, I would hope the list moderator would step in here with a
refresher of what is / is not proper lines of discussion permitted.
----- Original Message -----
From: "Mike Willochell" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, November 26, 2002 4:32 PM
Subject: Re: Edits Being Overwritten Bug - Work Around
> At 07:36 AM 11/27/2002 +1100, Tom Grimshaw wrote:
> >I don't know if RBTI are going to have time to get around to this
> >prior to "closing the books" on 6.5++ so here is a workaround for
> >anyone who applies the latest patch and encounters the edits not
> >being saved bug.
> >
> >Just go back to version 1.851 where the problem does not exist.
>
> Dear Mr. Grimshaw;
>
> With all due respect, I must say that encouraging the R:BASE community to
> revert to an antiquated build of R:BASE 6.5++ is quite counterproductive
and
> not a very wise move. So many things have been fixed and added to the
latest
> build that down-grading to the 1.851 build is like trading in a 2002 BMW
for a
> 1990 Yugo (no offense intended to all the Yugo lovers out there!)
>
> In a message dated 11/25/2002, the staff at RDCC requested that you send a
> sample of the anomaly so that we could verify whether or not it was an
issue
> that needed to be addressed. As of this moment, we have not received
> anything on your behalf relating to this issue.
>
> To date, the R:BASE community, both private and public, has been testing
the
> latest 1.861 build with great enthusiasm, and has not reported any
problems in
> this area of the forms package.
>
> Another important issue to consider is that as the versions and builds
> progress,
> we are doing our best to weed out all the inconsistencies and improper
> behavior
> of prior versions. In using the older versions, it is very common for a
> developer to
> use the logic of two "wrongs" to make a "right." Now, we have to be
reasonable
> when it comes to using the new logic of two "rights" to make a "right."
>
> On behalf of the entire R:BASE community and Development Staff, I think
that
> it is a grave injustice to make suggestions like the aforementioned. At
this
> point, the R:BASE Developers are well aware of how we work and handle
things
> like this, and also that there is a proper procedure that must be followed
> if any
> action is to be expected. To jump to such a premature conclusion is not
the
> proper or productive way.
>
> I would hope that you would direct your efforts towards narrowing down the
> issue, and sending a reliable and replicable example to the dedicated
folks at
> RDCC so that if there actually is a problem, we can get to work on it.
>
> Respectfully,
>
> Mike WIllochell
>
> ================================================
> 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/
