Nor was my message intended to express any negative reading of your message.
It was merely to underscore your observations.

Emmitt Dove
Manager, DairyPak Business Systems
Evergreen Packaging, Inc.
[EMAIL PROTECTED]
[EMAIL PROTECTED]
(203) 643-8022


-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Wills, Steve
Sent: Thursday, July 10, 2008 1:23 PM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Re: Database Limits, again?

I agree.  Just to be sure about my meaning, there was no veiled
implication that anybody, anywhere, had been remiss in this or any other
area.  My meaning was:
- to express my positive impression about what RBTI did and how
(quickly) they did it
- to express my curiosity about what must be superlative management of
their source 

Sorry if anything might have been construed as questioning for something
potentially negative ... if anyone did take my meaning that way.

I am impressed and just really curious as to how they manage to be so
impressive, especially in this area of code/source management, which is,
IMHO, a sine qua non of quick (and good/reliable) fixes and updates, as
well as long-term development of the product.


Steve

-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Emmitt
Dove
Sent: Thursday, July 10, 2008 12:15pm 12:15
To: RBASE-L Mailing List
Subject: [RBASE-L] - Re: Database Limits, again?

Steve,

It has been my experience that once in a great while we stumble across
something that no one had ever hit before - at least no one had ever
identified the issue - and when you can give RBTI the database and the
clearly-defined steps to get there, they can find and fix legacy issues.

Emmitt Dove
Manager, DairyPak Business Systems
Evergreen Packaging, Inc.
[EMAIL PROTECTED]
[EMAIL PROTECTED]
(203) 643-8022


-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Wills,
Steve
Sent: Thursday, July 10, 2008 12:40 PM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Re: Database Limits, again?

Oh, Mike, I appreciate the implied something-about-me, but, to tell you
the truth, I don't know if it's easy "to put into words how wonderful
life is, while you'R:e in the world", with apologies to Elton John and
Bernie Taupin and, perhaps, all of y'all as well as RBTI.  Truly, the
ridiculously short cycle-time for this fix is impressive.

It also causes me to have some thoughts/questions:
- Had this problem ever been described/identified in ANY version?
- (If not), the R:Team must be jam-up and jelly-tight on managing their
code library ...?
- My wife often says, "I'd rather be lucky than good."  This is a fine
philosophy, 
  which she accepts but doesn't pursue, as it's certainly not a reliable
strategy.  
  However, even if by some confluence of variables within the Time-Space
continuum, 
  this fix was just one of those ultra-low-hangin' fruits, as it turned
out, 
  it's still WAY AWESOME, man!

Hope that was sufficiently and appropriately superlative. ;-)

Nice job, RBTI.


Steve in Memphis

 
-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of MikeB
Sent: Wednesday, July 09, 2008 8:52pm 20:52
To: RBASE-L Mailing List
Subject: [RBASE-L] - Re: Database Limits, again?


----- Original Message ----- 
From: "A. Razzak Memon" <[EMAIL PROTECTED]>
To: "RBASE-L Mailing List" <[email protected]>
Sent: Wednesday, July 09, 2008 7:48 PM
Subject: [RBASE-L] - Re: Database Limits, again?


> At 06:50 PM 7/9/2008, [EMAIL PROTECTED] wrote:
>
>>Razzak:
>>
>>Thanks for fixing the problem! Who knows how far back this goes?
>
>
> Amazing, isn't it?
>

 Amazing doesn't quite describe it really...

I don't think we can come up with superlatives (well probably Steve W.
can 
((-; ) to describe the extraordinary effort you guys make to drive the
product 
to perfection.


> You submitted the request and sent the file to R:DCC at
> 5:33pm (Eastern Time) and the LEGACY problem was FIXED at
> 6:15pm (Eastern Time) with a complimentary notification to
> you as well.
>
> Razzak.
> 


Reply via email to