Introduction of Calling Quick Screens as Functions
chuck.reinke
chuck.reinke@sbcglobal.net
Wed, 26 May 2004 20:48:33 -0700
This is a multi-part message in MIME format.
------=_NextPart_000_0008_01C44362.CF223CC0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Blue,
I mean that the more normalized the data structures, the less the need =
for procedure code with Quick.=20
Chuck
----- Original Message -----=20
From: Robert Edis=20
To: PowerHouse List=20
Sent: Wednesday, May 26, 2004 1:53 PM
Subject: Re: Introduction of Calling Quick Screens as Functions
Chuck
You say here that PH is a language for NORMALIZED data yet you then =
say Quick offers a solution for multi-dimensional programming. OLAP or =
multi-dimension data is usually DENORMALISED. =20
I'm confused.
Blue
"chuck.reinke" <chuck.reinke@sbcglobal.net> wrote:
On the subject of perverting Quick, you can think of PowerHouse as a =
language for NORMALIZED data, which most of us learned (painfully by =
experinece) was the best way to organize business records.=20
Yet not all computing is for business records. Statistics, for =
example, often means mulitdimensional computing. So when it comes to =
multidimensional programming, Quick offers a solution. =20
To complicate things further, you can use multiple processes and use =
the output of a (Quiz,QTP, QUICK) process as the input to a QUICK =
process.
Set up a file equation to direct QKIN to the process and let it rip. =
As I remember, the QKIN file needs to be a semicolon delimited file.
I was once involved in developing a student scheduling project, with =
students, teachers, rooms, classes, and times, that used this approach =
quite successfully.
Chuck
------=_NextPart_000_0008_01C44362.CF223CC0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR></HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Blue,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I mean that the more normalized the =
data=20
structures, the less the need for procedure code with Quick. =
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Chuck</FONT></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV=20
style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
<A title=3Drobeconsult@sbcglobal.net=20
href=3D"mailto:robeconsult@sbcglobal.net">Robert Edis</A> </DIV>
<DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3Dpowerh-l@lists.sowder.com=20
href=3D"mailto:powerh-l@lists.sowder.com">PowerHouse List</A> </DIV>
<DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Wednesday, May 26, 2004 =
1:53=20
PM</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Subject:</B> Re: Introduction of =
Calling=20
Quick Screens as Functions</DIV>
<DIV><BR></DIV>
<DIV>Chuck</DIV>
<DIV> </DIV>
<DIV>You say here that PH is a language for NORMALIZED data yet you =
then say=20
Quick offers a solution for multi-dimensional programming. OLAP =
or=20
multi-dimension data is usually DENORMALISED. </DIV>
<DIV> </DIV>
<DIV>I'm confused.</DIV>
<DIV> </DIV>
<DIV>Blue<BR><BR><B><I>"chuck.reinke" <<A=20
=
href=3D"mailto:chuck.reinke@sbcglobal.net">chuck.reinke@sbcglobal.net</A>=
></I></B>=20
wrote:</DIV>
<BLOCKQUOTE class=3Dreplbq=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px =
solid">
<META content=3DWord.Document name=3DProgId>
<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR>
<META content=3D"Microsoft Word 10" name=3DOriginator><LINK=20
href=3D"cid:filelist.xml@01C44302.49753470" rel=3DFile-List>
<STYLE>@font-face {
font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; =
mso-header-margin: .5in; mso-footer-margin: .5in; mso-paper-source: 0; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline; text-underline: single
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline; text-underline: single
}
P.MsoAutoSig {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New Roman"
}
LI.MsoAutoSig {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New Roman"
}
DIV.MsoAutoSig {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New Roman"
}
P {
FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: =
"Times New Roman"; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto
}
SPAN.EmailStyle16 {
COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal; =
mso-style-noshow: yes; mso-ansi-font-size: 10.0pt; =
mso-ascii-font-family: Arial; mso-hansi-font-family: Arial; =
mso-bidi-font-family: Arial
}
SPAN.EmailStyle20 {
COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply; =
mso-style-noshow: yes; mso-ansi-font-size: 10.0pt; =
mso-ascii-font-family: Arial; mso-hansi-font-family: Arial; =
mso-bidi-font-family: Arial; mso-bidi-font-size: 10.0pt
}
SPAN.GramE {
mso-style-name: ""; mso-gram-e: yes
}
DIV.Section1 {
page: Section1
}
OL {
MARGIN-BOTTOM: 0in
}
UL {
MARGIN-BOTTOM: 0in
}
</STYLE>
<DIV><FONT face=3DArial size=3D2>On the subject of perverting Quick, =
you can=20
think of PowerHouse as a language for NORMALIZED data, which most of =
us=20
learned (painfully by experinece) was the best way to organize =
business=20
records. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Yet not all computing is for =
business records.=20
Statistics, for example, often means mulitdimensional computing. So =
when it=20
comes to multidimensional programming, Quick offers a =
solution. =20
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>To complicate things further, you =
can use=20
multiple processes and use the output of a (Quiz,QTP, QUICK) process =
as the=20
input to a QUICK process.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Set up a file equation to direct =
QKIN to the=20
process and let it rip. As I remember, the QKIN file needs to be a =
semicolon=20
delimited file.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I was once involved in developing a =
student=20
scheduling project, with students, teachers, rooms, classes, and =
times, that=20
used this approach quite successfully.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial=20
size=3D2>Chuck</FONT></DIV></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_0008_01C44362.CF223CC0--