Introduction of Calling Quick Screens as Functions
chuck.reinke
chuck.reinke@sbcglobal.net
Wed, 26 May 2004 08:32:31 -0700
This is a multi-part message in MIME format.
------=_NextPart_000_001D_01C442FB.FCB8A3C0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
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_001D_01C442FB.FCB8A3C0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns:eXclaimer =3D "http://www.exclaimer.co.uk"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<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><!--[if gte =
mso 9]><xml>
<o:OfficeDocumentSettings>
<o:DoNotRelyOnCSS/>
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:SpellingState>Clean</w:SpellingState>
<w:GrammarState>Clean</w:GrammarState>
<w:DocumentKind>DocumentEmail</w:DocumentKind>
<w:EnvelopeVis/>
<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
</w:WordDocument>
</xml><![endif]-->
<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>
<!--[if gte mso 10]>
<style>
/* Style Definitions */=20
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:10.0pt;
font-family:"Times New Roman";}
</style>
<![endif]--><!--[if gte mso 9]><xml>
<u1:OfficeDocumentSettings>
<u1:DoNotRelyOnCSS/>
</u1:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<u2:WordDocument>
<u2:Zoom>0</u2:Zoom>
<u2:DocumentKind>DocumentEmail</u2:DocumentKind>
<u2:EnvelopeVis/>
</u2:WordDocument>
</xml><![endif]--></HEAD>
<BODY lang=3DEN-US style=3D"tab-interval: .5in" vLink=3Dpurple =
link=3Dblue=20
bgColor=3D#ffffff><![if !supportLists]><![endif]><![if =
!supportLists]><![endif]><![if !supportLists]><![endif]><![if =
!supportLists]><![endif]><![if !supportLists]><![endif]><!--[if =
supportFields]><span=20
class=3DEmailStyle16><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;mso-bidi-font-size:12.0pt'><span =
style=3D'mso-element:field-begin'></span><span=20
style=3D'mso-spacerun:yes'> </span>AUTOTEXTLIST \s "E-mail =
Signature" <span=20
style=3D'mso-element:field-separator'></span></span></font></span><![endi=
f]--><!--[if supportFields]><span=20
class=3DEmailStyle16><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;mso-bidi-font-size:12.0pt'><span =
style=3D'mso-element:field-end'></span></span></font></span><![endif]-->
<DIV><FONT face=3DArial size=3D2>On the subject of perverting Quick, you =
can think=20
of PowerHouse as a language for NORMALIZED data, which most of us =
learned=20
(painfully by experinece) was the best way to organize business 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 multiple=20
processes and use the output of a (Quiz,QTP, QUICK) process as the input =
to a=20
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 size=3D2>Chuck</FONT></DIV></BODY></HTML>
------=_NextPart_000_001D_01C442FB.FCB8A3C0--