David,

I just assumed that everybody probably knew but no-one had mentioned it to
Dan - I get lots of things like that where everybody knows but me <g>.

I almost didn't bother to send that e-mail but I'm glad I did - so long as
you don't charge for your damaged socks!

Regards, Alastair.

----- Original Message -----
From: "David Blocker" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, April 12, 2002 10:52 AM
Subject: Re: Trouble with REPORTS


> Alastair
>
> Whoa, where did you figure THIS out!  I thought I knew all the tricks of
> this screen having taught folks the joys of it for years!  Even better,
when
> you save the view and return to the R> prompt, R:Base shows you the syntax
> for assigning column names in a view:
>
> CREATE VIEW viewname (alias1,alias2,alias3,alias4) AS SELECT T1.Col1,
> T1.Col1,T2.Col3,T2.Col4 FROM table1 T1, table2 T2 WHERE T1.PKCol =
T2.FKCol
>
> THis is amazing!  My socks are flying around the room!
>
> It even leads me to suggest  two enhancement requests for user
friendliness.
> The current screen that comes up lists all the names on the left, and the
> suggested aliases on the right.  In the example I did with this structure:
>
> Table1 = Account
> Table 2 = Invoices
> Linking col = AcctNo
>
> The SELECT was:
>
> SELECT T1.AcctName,T1.City,T1.State,T2.InvNum +
> FROM Account T1, Invoices T2 +
> WHERE T1.AcctNo = T2.AcctNo
>
> The alias screen shows:
>
> Column Name        Alias Name
>
> T1.AcctName        AcctName
> T1.City                    City
> T1.State                    State
> T2.InvNum            InvNum
>
> So first of all, a plus, R:Base simply guesses you want the column names
> minus the table designations.
>
> But to change an alias, you highlight the column whose alias you want to
> modify, click on a button at the bottom that says "Modify Current
Selection"
> and the alias comes up.  You change the alias, say "AcctName" to
"Company".
> You then click on the check box at the bottom that says "use Column
Aliases)
> and click on OK.
>
> R:Base then prompts:  "Do you wish to save your modifications to the alias
> name?" with Yes/No.  If you click on YES, you are returned to the query
> screen.
>
> And THAT's the first requested enhancment. It means you must repeat the
> whole sequence to change another alias name.  Instead, allow the user to
> change multiple aliases on the screen at once, THEN click OK to save them
> all.
>
> Second enhancement request: redesign this screen to make the many options
> more obvious. Why hide this and leave to the chance of a random mouse
click
> to discover it!  Ya can't knock their socks off if they can't see what's
> possible!
>
> But that's minor - what a great teaching tool and alternative for tired
> fingers!!!
>
> David Blocker
>
> ----- Original Message -----
> From: "Alastair Burr" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, April 11, 2002 6:27 PM
> Subject: Re: Trouble with REPORTS
>
>
> > > 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.
> >
> > Dan,
> >
> > If you right-click in the left-hand panel of the view-designer (but not
on
> > any on the boxes) you get a menu box popped-up with an alias name option
> > (among other things). From there you can change the names of your
columns
> > for the view in question.
> >
> > Razzak/Anybody - what is the current limit on table/column names being
> > different? As I remember, it used to be the first 8 characters but I
> though
> > it had changed in more recent versions. Is it the full 18 characters now
> or
> > is there still some lower limit?
> >
> > Regards, Alastair.
> >
> >
> > ----- Original Message -----
> > From: "Dan" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Thursday, April 11, 2002 3:38 PM
> > 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