Sami:
We do not get into arguments at this list <g> LOL...we have intelligent
discussions that enlighten and make us all better developers. I can honestly
say that I have learnt something new from every "discussion" in the list,
the day we stop "discussing" we stop learning.
Javier,

Javier Valencia, PE
President
Valencia Technology Group, L.L.C.
14315 S. Twilight Ln, Suite #14
Olathe, Kansas 66062-4578
Office (913)829-0888
Fax (913)649-2904
Cell (913)915-3137
================================================
Attention:
The information contained in this message and or attachments is intended
only for the person or entity to which it is addressed and may contain
confidential and/or privileged material.  Any review, retransmission,
dissemination or other use of, or taking of any action in reliance upon,
this information by persons or entities other than the intended recipient
is prohibited. If you received this in error, please contact the sender and
delete the material from all system and destroy all copies.
======================================================

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Sami Aaron
Sent: Tuesday, August 24, 2004 12:37 PM
To: RBG7-L Mailing List
Subject: [RBG7-L] - RE: Computed columns - different expressions

The difference is that using RBDefine, I can SEE the original computed
definition and so if I decide to make a change, it's obvious that I'm making
a change.  In a command file, there is NO notice or indication of a
difference.

I'm not looking to get into an argument - I just spent a couple of hours
trying to determine how and why an expression on a temporary table was
evaluating incorrectly when I had already fixed it once - but obviously in a
different table.  I had a level of understanding in my mind about engine
restrictions and I'm simply trying to get a handle on how other developers
handle this.

Sami

> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of A. Razzak
> Memon
> Sent: Tuesday, August 24, 2004 11:51 AM
> To: RBG7-L Mailing List
> Subject: [RBG7-L] - RE: Computed columns - different expressions
>
>
> At 11:36 AM 8/24/2004 -0500, Sami Aaron you wrote:
>
> >But if you're creating the tables via command files,
> >there still is no warning or indication of a difference.
>
> Do you get the -WARNING- when doing the same in RBDEFine?
>
> Very Best R:egards,
>
> Razzak.
>
>
>  > -----Original Message-----
> > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of A. Razzak
> > > Memon
> > > Sent: Tuesday, August 24, 2004 11:17 AM
> > > To: RBG7-L Mailing List
> > > Subject: [RBG7-L] - RE: Computed columns - different expressions
> > >
> > >
> > > At 11:08 AM 8/24/2004 -0500, Javier Valencia wrote:
> > >
> > > >A compromise would be to have the Data Dictionary bring up the
> > > >definition when adding columns to a table in the Designer, but
> > > >allow the user to override the definition without further checks.
> > >
> > > And that's exactly how it works in 6.5++, 7.x and R:BASE Turbo V-8
> > > "Data Designers" (RBDEFine).
> > >
> > > Very Best R:egards,
> > >
> > > Razzak.
> > >
> > >
> > >
> > >
>
>
>
>

Reply via email to