IMO, CREATE VIEW through code is the only way to go.  Even in the old (DOS
TEXT MODE) days, I wasn't a huge fan of Query-By-Design or whatever the
monikor.  I hate the one in ACCESS and I ain't happy about the GUI on in
RBWIN either.

However, that's all moot once I learned about cor-related SELECTs.  Using
this approach, you can test your SELECT-statement before you define the
view.  I usually test it at the command line with only the minimally
required COL's.  Then I put it into a command file.  I also have a "funny"
way of indenting these in my code - example below.  It looks a bit
screen-real-estate consuming, but this presentation allows me to make a
simple and quick count of all the "paired" elements in view DDL.  Lemme'
tell you, that little ability alone has saved me lots of time, especially
compared to doing the whole thing at the command line.

-- *****************************************************************
-- CREATE VIEW DDL
CREATE VIEW vEWC_JDB_SEQ_B4 +
  (SSN,+
   SecondaryActivity,+
   WYQ,+
   FYQTRAtEntry,+
   FYQTRAtExit,+
   CHRONOSequence,+
   FYQEntrySequence,+
   FYQExitSequence,+
   RelativeSequence,+
   WYQEarningsSUM +
  ) +
AS +
SELECT +
   ewc.SSN,+
   jdb.SecondaryActivity,+
   ewc.WYQ,+
   jdb.FYQTRAtEntry,+
   jdb.FYQTRAtExit,+
   ewc.CHRONOSequence,+
   jdb.FYQEntrySequence,+
   jdb.FYQExitSequence,+
   ewc.RelativeSequence,+
   ewc.WYQEarningsSUM +
FROM +
   ESUI_WYQSSN_CTSUM ewc, +
   JOHNs_DATA_B jdb +
WHERE +
   ewc.SSN=jdb.SSN +
AND +
   jdb.MINSECACTEntryDate BETWEEN '01/01/1997' AND '09/30/1999' +
AND +
   jdb.MAXSECACTExitDate BETWEEN '01/01/1997' AND '09/30/1999' +
AND +
   jdb.SSN IN (SELECT SSN +
               FROM ACTIVITIES_SKIP_A +
               WHERE HowManyEQY = 'YYY' )

-- *****************************************************************

Later,
Steve in Memphis

> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of Dan
> Sent: Thursday, April 11, 2002 10:22 AM
> To: [EMAIL PROTECTED]
> Subject: RE: Trouble with REPORTS
>
>
> Steve,
>    Thanks, I did see it earlier (it is what prompted me to correctly name
> my post) but was told that my problem was due to a bug in the 6.5
> version I
> was using and upgrading would allow me to use my longer
> tablenames,columnnames.  I see this is incorrect and will have to use a
> workaround.  Hopefully version seven fixes this bug.
>
> I appreciate everyones help. I will now learn how to create a view using
> code rather than the built in view designer. I see Dr.R has posted an
> example of this,and I am on my way to doing just such. I will report (no
> pun intended) if this fixes my report problem.
>
> Dan
>
> At 10:03 AM 4/11/2002 -0500, you wrote:
> >Dan, I sent this in an earlier mail, "Trouble with FORMS", so maybe you
> >didn't see it.  I don't know, but it might help if that 18-char
> issue is the
> >problem.
> >
> >When I CREATE VIEW, I ALWAYS use the (COLName1,COLName2 ...)
> "alias" feature
> >before the "AS ...", even if I'm just using the same name as the source
> >COLUMN.
> >
> >HTH.
> >
> >Later,
> >Steve in Memphis
> >
> > > -----Original Message-----
> > > From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On
> > > Behalf Of Dan
> > > Sent: Thursday, April 11, 2002 9:39 AM
> > > To: [EMAIL PROTECTED]
> > > Subject: Trouble with REPORTS
> > >
> > >
> > > Ok,
> > >    Starting over.  I am now using the latest greatest version
> > > 6.5++  build
> > > 1.851xRT03.
> > >
> > > Without performing the work around suggested earlier (select as for my
> > > view) I recreated my view with R:Bases' view designer. Created a new
> > > Report. Placed 4 columns on the report. Saved it. Ran it... and
> > > crashed.  Restarted Rbase and looked at the form. Guess what.
> One of my
> > > columns is GONE.    I moved another just slightly, and tried to
> > > save.....  Hmmm, now the one that is gone is out of the margin
> > > (this rings
> > > a bell)
> > > (Bill, yes I tried the select all in each area.... that
> column does not
> > > exist. (maybe it is out of phase with this reality))
> > > So... now what.  Back to workarounds? or should I just learn to
> > > not create
> > > columns in my tables that have nice descriptive names like
> > > FRRepGroupNum  or FRGroupInactivate.
> > >
> > > Yes, I did show version to be sure I am running the latest.
> > > Yes, I did check for lost or stray things on the report.
> > > Yes, I now have less hair than I did yesterday.
> > >
> > > Next Idea?
> > >
> > > I didn't try creating the view with aliases yet as it is not a
> > > function of
> > > the view designer. It would have to be done with code, and I
> haven't ever
> > > created a view with code yet.
> > >
> > >
> > > Thanks,
> > > Dan
> > >
> > >
> > >
> > > Dan Champion
> > > Champion Solutions
> > > www.championsolutions.net
> > > (616) 453-7225
> > >
> > >
> > > ================================================
> > > 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/
>
>
> ================================================
> 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