some SQL reference
Richard Sheehan
sheerich@isu.edu
Thu, 28 Apr 2005 11:00:16 -0600
Hmm.
How about "reading" directions and posting accordingly?
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of powerh-l digest..."
>
>
Richard Sheehan
IT Programmer Analyst
208-282-4427
Student Services, College of Technology
Idaho State University
Pocatello, ID 83209-8380
Jody Burgess ISP wrote:
>See SQLServerCentral.com or SSWUG.org for information on SQL Server.
>
>Jody Burgess ISP
>
>-----Original Message-----
>From: powerh-l-admin@lists.sowder.com
>[mailto:powerh-l-admin@lists.sowder.com]On Behalf Of
>powerh-l-request@lists.sowder.com
>Sent: Thursday, April 28, 2005 5:11 AM
>To: powerh-l@lists.sowder.com
>Subject: powerh-l digest, Vol 1 #1338 - 4 msgs
>
>
>Send powerh-l mailing list submissions to
> powerh-l@lists.sowder.com
>
>To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.sowder.com/mailman/listinfo/powerh-l
>or, via email, send a message with subject or body 'help' to
> powerh-l-request@lists.sowder.com
>
>You can reach the person managing the list at
> powerh-l-admin@lists.sowder.com
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of powerh-l digest..."
>
>
>Today's Topics:
>
> 1. RE:database trigger (Robert Edis)
> 2. Re:Quick screen (Richard Sheehan)
> 3. RE:Quick screen (Joe Boyle)
> 4. RE:Function Key labels on Windows (Peter Bateman)
>
>--__--__--
>
>Message: 1
>Date: Wed, 27 Apr 2005 11:38:41 -0700 (PDT)
>From: Robert Edis <robeconsult@sbcglobal.net>
>Subject: RE: database trigger
>To: PowerHouse List <powerh-l@lists.sowder.com>
>
>MS SQL Server has less overall functionality than any
>Oracle RDBMS. It does have table triggers, stored
>procedures and formula columns.
>
>In how many places can SSNUMS be modified?
>If this column is NEVER modified, i.e. ony its
>components SSNUMBER and STATUS are modifiable, then
>using a calculated formula column in the table may be
>best. You may still need to refresh the data record
>on the form after an update though. If you can't
>modify the table structure then use a standard stored
>procedure that you can call from any form to update
>the column. Stored procedures are predictable and
>visable to developers.
>
>If the same columns are labeled differently in
>different peices of code I suggest you "bite the
>bullet" and introduce some standardisation now before
>more time is wasted on fixing poorly written code.
>
>Blue
>
>
>--- Viet Nguyen <VNguyen@wsboces.org> wrote:
>
>
>
>>The problem I have is that we have so many instances
>>in qtp & quick that
>>sometime refer to SSNUMR and other times refer to
>>SSNUM or just STATUS
>>alone. I was trying to avoid going to all of these
>>millions lines of
>>codes and have to logically & physically change
>>them.
>>
>>Do you know if MSSQL has better handling for this?
>>
>>
>>-----Original Message-----
>>From: powerh-l-admin@lists.sowder.com
>>[mailto:powerh-l-admin@lists.sowder.com] On Behalf
>>Of Robert Edis
>>Sent: Wednesday, April 27, 2005 2:18 PM
>>To: PowerHouse List
>>Subject: RE: database trigger
>>
>>Viet
>>
>>Database table triggers are tricky and sometimes
>>unpredictable. They also represent "hidden" logic
>>in
>>that future maintenance programmers may be unaware
>>of
>>it when making changes to any code that touches that
>>table. I would avoid triggers unless they were the
>>only option.
>>
>>As Joe says doing the logic in a field process
>>procedure is probably the best way to acheive what
>>you
>>want.
>>
>>There are two other database options available to
>>you
>>as well but either may require a re-fetch of the
>>data
>>if SSNUMS is displayed on the PH form. These are:
>>
>>1. a stored procedure run from the PH form
>>2. a calculated (formula) column in the database
>>
>>That latter can never be modified as it is only the
>>result of a calculation using other table columns.
>>
>>Regards,
>>
>>Blue
>>
>>
>>--- Joe Boyle <atla38@dsl.pipex.com> wrote:
>>
>>
>>
>>>if you do an update stay, you would have to modify
>>>the PH code anyway
>>>because the trigger will alter the row contents
>>>
>>>
>>and
>>
>>
>>>the checksum value for
>>>subsequent puts. You would then have to do another
>>>get to update the
>>>checksum. You might as well add process procedures
>>>on each of the two fields
>>>to handle the changes.
>>>
>>>Regards, Joe.
>>>
>>>
>>>-----Original Message-----
>>>From: powerh-l-admin@lists.sowder.com
>>>[mailto:powerh-l-admin@lists.sowder.com] On Behalf
>>>Of Viet Nguyen
>>>Sent: 27 April 2005 14:46
>>>To: powerh-l@lists.sowder.com
>>>Subject: database trigger
>>>
>>>Hi All,
>>> I am migrating c-isam to oracle db and I have a
>>>question.
>>> 1) I have a field SSNUMS which has a
>>>
>>>
>>substructure
>>
>>
>>>SSNUMBER & STATUS.
>>> To eliminate modification to power code I am
>>>thinking about using
>>>trigger table trigger that will UPDATE the higher
>>>structure SSNUMS when
>>>there is an update is done on SSNUMBER or STATUS.
>>>Could someone give me
>>>some advise on how powerhouse handles the update
>>>
>>>
>>or
>>
>>
>>>how to create the
>>>trigger so that it doesn't recursively call on
>>>itself?
>>>Thanks.
>>>Viet.
>>>
>>>
>>>-----Original Message-----
>>>From: powerh-l-admin@lists.sowder.com
>>>[mailto:powerh-l-admin@lists.sowder.com] On Behalf
>>>Of Ken Langendock
>>>Sent: Friday, April 22, 2005 11:32 AM
>>>To: roger32909@bellsouth.net; Martin McDonough
>>>Cc: powerh-l@lists.sowder.com
>>>Subject: Re: RE: force a FIND?
>>>
>>>Ok let me clarify this for you.
>>>
>>>screen a
>>>
>>>temp t-xyz-key char(??)
>>>
>>>file XYZ primary
>>>access via xyz-key usign t_xyz-key
>>>access via xyz-key request xyz-key
>>>
>>>procedure x ; can be procedure entry/find/whatever
>>>begin
>>> run screen b
>>> push find ; invokes once this procedure ends
>>> let t_xyz-key = xyz-key of XYZ
>>>end
>>>
>>>procedure path
>>>begin
>>> if " " ne t-xyz-key
>>> then let path = 1
>>> else prompt xyz-key
>>>end
>>>
>>>procedure postfind
>>>let t_xyz-key = " " ; clear it out for next find
>>>
>>>
>>>
>>>If you want more clarification....send me the
>>>
>>>
>>screen
>>
>>
>>>code.
>>>
>>>Ken
>>>
>>>--- roger32909@bellsouth.net wrote:
>>>
>>>
>>>>Already tried PUSH FIND. This still required
>>>>
>>>>
>>user
>>
>>
>>>>intervention to Find the updated record.
>>>>
>>>>REFRESH does not do a FIND.
>>>>
>>>>The PRIMARY file XYZ record is NOT passed to the
>>>>called screen.
>>>>In the called screen, the file XYZ is a DESIGNER
>>>>file.
>>>>
>>>>Agree with you, Martin, but unfortunately the
>>>>subscreen is called from many other screens, so
>>>>
>>>>
>>it
>>
>>
>>>>is not possible to pass the record.
>>>>
>>>>
>>>>
>>>>>From: "Martin McDonough"
>>>>>
>>>>>
>>>><martin.mcdonough@rosebys.com>
>>>>
>>>>
>>>>>Date: 2005/04/22 Fri AM 10:17:25 EDT
>>>>>To: <roger32909@bellsouth.net>
>>>>>Subject: RE: force a FIND?
>>>>>
>>>>>If possible, the correct way to do this would
>>>>>
>>>>>
>>be
>>
>>
>>>>to pass the primary
>>>>
>>>>
>>>>>file 'XYZ' to the subscreen and display the
>>>>>
>>>>>
>>>field
>>>
>>>
>>>>from the 'passed' file
>>>>
>>>>
>>>>>on the subscreen.
>>>>>
>>>>>By putting 'REFRESH' on the field statement of
>>>>>
>>>>>
>>>the
>>>
>>>
>>>>main screen, after
>>>>
>>>>
>>>>>the update is done in the subscreen and you
>>>>>
>>>>>
>>>return
>>>
>>>
>>>>to the main screen,
>>>>
>>>>
>>>>>the value will be automatically refreshed.
>>>>>
>>>>>Regards
>>>>>
>>>>>Martin McDonough
>>>>>
>>>>>-----Original Message-----
>>>>>From: powerh-l-admin@lists.sowder.com
>>>>>[mailto:powerh-l-admin@lists.sowder.com] On
>>>>>
>>>>>
>>>Behalf
>>>
>>>
>>>>Of
>>>>
>>>>
>>>>>roger32909@bellsouth.net
>>>>>Sent: 22 April 2005 15:07
>>>>>To: powerh-l@lists.sowder.com
>>>>>Subject: force a FIND?
>>>>>
>>>>>OpenVMS 7.3 PH 7.10.G1
>>>>>
>>>>>We have an old screen that works this way:
>>>>>
>>>>>The PRIMARY file in the main screen is XYZ.
>>>>>
>>>>>
>=== message truncated ===
>
>
>--__--__--
>
>Message: 2
>Date: Wed, 27 Apr 2005 13:50:51 -0600
>From: Richard Sheehan <sheerich@isu.edu>
>Subject: Re: Quick screen
>To: Robert Edis <robeconsult@sbcglobal.net>
>Cc: PowerHouse List <powerh-l@lists.sowder.com>
>
>Blue,
>
>I remember being able to create a temp item "occurs with " clause, or
>just "occurs NN". I'm not sure which, but I think that is no longer
>allowed - qdesign will complain about it.
>
>Richard
>
>Richard Sheehan
>IT Programmer Analyst
>208-282-4427
>Student Services, College of Technology
>Idaho State University
>Pocatello, ID 83209-8380
>
>
>
>Robert Edis wrote:
>
>
>
>>Doesn't one have to create an array with a temp field
>>(occurs ...) to use the occurence reference?
>>
>>Blue
>>
>>--- Richard Sheehan <sheerich@isu.edu> wrote:
>>
>>
>>
>>
>>>I believe you can use the occurrence and bracketed
>>>notation to get to
>>>the values that you are trying to reference.
>>>
>>>I don't have any manuals to reference, so you will
>>>need to look these
>>>commands up.
>>>
>>>
>>>---
>>>Richard Sheehan
>>>IT Programmer Analyst
>>>208-282-4427
>>>Student Services, College of Technology
>>>Idaho State University
>>>Pocatello, ID 83209-8380
>>>
>>>
>>>
>>>Joe Boyle wrote:
>>>
>>>
>>>
>>>
>>>
>>>>can it be assumed that you know how to code the
>>>>
>>>>
>>>>
>>>>
>>>linkage that will retrieve
>>>
>>>
>>>
>>>
>>>>the records that contain the previous int-amt ? I
>>>>
>>>>
>>>>
>>>>
>>>ask this because you
>>>
>>>
>>>
>>>
>>>>are'nt showing very much qdesign syntax so far.
>>>>
>>>>Regards, Joe.
>>>>
>>>>
>>>>-----Original Message-----
>>>>From: powerh-l-admin@lists.sowder.com
>>>>[mailto:powerh-l-admin@lists.sowder.com] On Behalf
>>>>
>>>>
>>>>
>>>>
>>>Of terry terry
>>>
>>>
>>>
>>>
>>>>Sent: 26 April 2005 18:43
>>>>To: powerh-l@lists.sowder.com
>>>>Subject: Quick screen
>>>>
>>>>
>>>>Hi,
>>>> I have a Quick screen (PH 7.10.G3) whereby every
>>>>
>>>>
>>>>
>>>>
>>>second half of the year
>>>
>>>
>>>
>>>
>>>> before interest could be calculated, the
>>>>
>>>>
>>>>
>>>>
>>>previous int-amt has to be
>>>
>>>
>>>
>>>
>>>>subtracted from the b/f amount(brought forward
>>>>
>>>>
>>>>
>>>>
>>>amount). The problem for me
>>>
>>>
>>>
>>>
>>>>is that these fields are cluster fields and so I
>>>>
>>>>
>>>>
>>>>
>>>have no way of
>>>
>>>
>>>
>>>
>>>>referencing a previous field .Can you please help.
>>>>
>>>>
>>>>
>>>>
>>>Thanks in advance.
>>>
>>>
>>>
>>>
>>>>Every second half of year:
>>>>int-amt= b/f amount - previous(int-amt) * interest
>>>>
>>>>
>>>>yr prt b/f amount cont amt tot-amt
>>>>
>>>>
>>>>
>>>>
>>>interest int-amt c/f amt
>>>
>>>
>>>
>>>
>>>>72 1 0 50.00
>>>>
>>>>
>>>>
>>>>
>>>50.00 4 % 2.00
>>>
>>>
>>>
>>>
>>>>52.00
>>>>72 2 52.00 100.00 152.00
>>>>
>>>>
>>>>
>>>>
>>> 3 % 1.50
>>>
>>>
>>>
>>>
>>>>151.50
>>>>73 1 151.50 50.00 201.50
>>>>
>>>>
>>>>
>>>>
>>> 5 % 7.58
>>>
>>>
>>>
>>>
>>>>209.08
>>>>73 2 209.08 100.00 309.08
>>>>
>>>>
>>>>
>>>>
>>>6 % 12.09
>>>
>>>
>>>
>>>
>>>>313.59
>>>>
>>>>
>>>>
>>>>
>>>>
>>>_________________________________________________________________
>>>
>>>
>>>
>>>
>>>>Express yourself instantly with MSN Messenger!
>>>>
>>>>
>>>>
>>>>
>>>Download today - it's FREE!
>>>
>>>http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
>>>
>>>
>>>
>>>
>>>>
>>>>
>>>>
>>>>
>>>--
>>>= = = = = = = = = = = = = = = = = = = = = = = = = =
>>>= =
>>>Mailing list: powerh-l@lists.sowder.com
>>>Subscribe: "subscribe" in message body to
>>>powerh-l-request@lists.sowder.com
>>>Unsubscribe: "unsubscribe <password>" in
>>>message body to powerh-l-request@lists.sowder.com
>>>http://lists.sowder.com/mailman/listinfo/powerh-l
>>>This list is closed, thus to post to the list you
>>>must be a subscriber.
>>>
>>>
>>>
>>>
>>>
>
>--__--__--
>
>Message: 3
>From: "Joe Boyle" <atla38@dsl.pipex.com>
>To: "'Richard Sheehan'" <sheerich@isu.edu>,
> "'Robert Edis'" <robeconsult@sbcglobal.net>
>Cc: "'PowerHouse List'" <powerh-l@lists.sowder.com>
>Subject: RE: Quick screen
>Date: Wed, 27 Apr 2005 21:31:23 +0100
>
>there are new'ish ( PH8 on ? ) limitations on temps but I think that it
>simply stops you adding 'reset at' syntax to temps that occur with
>files/tables.
>
>Also, you can't use item(n) syntax in quick, but only quiz/qtp - you have to
>use for loops in quick. And if you have repeating items in records
>referenced in clusters you have to use 'GHOST' screems ! :)
>
>Regards, Joe.
>
>
>
>-----Original Message-----
>From: powerh-l-admin@lists.sowder.com
>[mailto:powerh-l-admin@lists.sowder.com] On Behalf Of Richard Sheehan
>Sent: 27 April 2005 20:51
>To: Robert Edis
>Cc: PowerHouse List
>Subject: Re: Quick screen
>
>Blue,
>
>I remember being able to create a temp item "occurs with " clause, or
>just "occurs NN". I'm not sure which, but I think that is no longer
>allowed - qdesign will complain about it.
>
>Richard
>
>Richard Sheehan
>IT Programmer Analyst
>208-282-4427
>Student Services, College of Technology
>Idaho State University
>Pocatello, ID 83209-8380
>
>
>
>Robert Edis wrote:
>
>
>
>>Doesn't one have to create an array with a temp field
>>(occurs ...) to use the occurence reference?
>>
>>Blue
>>
>>--- Richard Sheehan <sheerich@isu.edu> wrote:
>>
>>
>>
>>
>>>I believe you can use the occurrence and bracketed
>>>notation to get to
>>>the values that you are trying to reference.
>>>
>>>I don't have any manuals to reference, so you will
>>>need to look these
>>>commands up.
>>>
>>>
>>>---
>>>Richard Sheehan
>>>IT Programmer Analyst
>>>208-282-4427
>>>Student Services, College of Technology
>>>Idaho State University
>>>Pocatello, ID 83209-8380
>>>
>>>
>>>
>>>Joe Boyle wrote:
>>>
>>>
>>>
>>>
>>>
>>>>can it be assumed that you know how to code the
>>>>
>>>>
>>>>
>>>>
>>>linkage that will retrieve
>>>
>>>
>>>
>>>
>>>>the records that contain the previous int-amt ? I
>>>>
>>>>
>>>>
>>>>
>>>ask this because you
>>>
>>>
>>>
>>>
>>>>are'nt showing very much qdesign syntax so far.
>>>>
>>>>Regards, Joe.
>>>>
>>>>
>>>>-----Original Message-----
>>>>From: powerh-l-admin@lists.sowder.com
>>>>[mailto:powerh-l-admin@lists.sowder.com] On Behalf
>>>>
>>>>
>>>>
>>>>
>>>Of terry terry
>>>
>>>
>>>
>>>
>>>>Sent: 26 April 2005 18:43
>>>>To: powerh-l@lists.sowder.com
>>>>Subject: Quick screen
>>>>
>>>>
>>>>Hi,
>>>> I have a Quick screen (PH 7.10.G3) whereby every
>>>>
>>>>
>>>>
>>>>
>>>second half of the year
>>>
>>>
>>>
>>>
>>>> before interest could be calculated, the
>>>>
>>>>
>>>>
>>>>
>>>previous int-amt has to be
>>>
>>>
>>>
>>>
>>>>subtracted from the b/f amount(brought forward
>>>>
>>>>
>>>>
>>>>
>>>amount). The problem for me
>>>
>>>
>>>
>>>
>>>>is that these fields are cluster fields and so I
>>>>
>>>>
>>>>
>>>>
>>>have no way of
>>>
>>>
>>>
>>>
>>>>referencing a previous field .Can you please help.
>>>>
>>>>
>>>>
>>>>
>>>Thanks in advance.
>>>
>>>
>>>
>>>
>>>>Every second half of year:
>>>>int-amt= b/f amount - previous(int-amt) * interest
>>>>
>>>>
>>>>yr prt b/f amount cont amt tot-amt
>>>>
>>>>
>>>>
>>>>
>>>interest int-amt c/f amt
>>>
>>>
>>>
>>>
>>>>72 1 0 50.00
>>>>
>>>>
>>>>
>>>>
>>>50.00 4 % 2.00
>>>
>>>
>>>
>>>
>>>>52.00
>>>>72 2 52.00 100.00 152.00
>>>>
>>>>
>>>>
>>>>
>>> 3 % 1.50
>>>
>>>
>>>
>>>
>>>>151.50
>>>>73 1 151.50 50.00 201.50
>>>>
>>>>
>>>>
>>>>
>>> 5 % 7.58
>>>
>>>
>>>
>>>
>>>>209.08
>>>>73 2 209.08 100.00 309.08
>>>>
>>>>
>>>>
>>>>
>>>6 % 12.09
>>>
>>>
>>>
>>>
>>>>313.59
>>>>
>>>>
>>>>
>>>>
>>>>
>>>_________________________________________________________________
>>>
>>>
>>>
>>>
>>>>Express yourself instantly with MSN Messenger!
>>>>
>>>>
>>>>
>>>>
>>>Download today - it's FREE!
>>>
>>>http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
>>>
>>>
>>>
>>>
>>>>
>>>>
>>>>
>>>>
>>>--
>>>= = = = = = = = = = = = = = = = = = = = = = = = = =
>>>= =
>>>Mailing list: powerh-l@lists.sowder.com
>>>Subscribe: "subscribe" in message body to
>>>powerh-l-request@lists.sowder.com
>>>Unsubscribe: "unsubscribe <password>" in
>>>message body to powerh-l-request@lists.sowder.com
>>>http://lists.sowder.com/mailman/listinfo/powerh-l
>>>This list is closed, thus to post to the list you
>>>must be a subscriber.
>>>
>>>
>>>
>>>
>>>
>--
>= = = = = = = = = = = = = = = = = = = = = = = = = = = =
>Mailing list: powerh-l@lists.sowder.com
>Subscribe: "subscribe" in message body to powerh-l-request@lists.sowder.com
>Unsubscribe: "unsubscribe <password>" in message body to
>powerh-l-request@lists.sowder.com
>http://lists.sowder.com/mailman/listinfo/powerh-l
>This list is closed, thus to post to the list you must be a subscriber.
>
>
>--__--__--
>
>Message: 4
>From: "Peter Bateman" <pfbcs@hotmail.com>
>To: powerh-l@lists.sowder.com
>Subject: RE: Function Key labels on Windows
>Date: Wed, 27 Apr 2005 22:25:55 -0300
>
>Don:
>
> I agree it is a shame that Cognos did not put Function key labels in QUICK
>NT.
>
> I was lucky in that in my case in that I had standard data context labels.
>
> It meant that each designer ## procedure
>
> starts off with DO INTERNAL DATA_LABELS
> as well as the APPEND and ENTRY procedures.
>
> At the end of each of the above DO INTERNAL ACTION_LABELS
>
>Both of this procedures displayed value in fields at the bottom of the
>screen.
>
> I considered trying to trap the keyboard entries. It used to be fairly
> simple in old 16 DOS but microsoft has made it more complicated. ( but not
>impossible )
> You might be able to trap the control characters in QUICK
>
>Define T1 integer size 1 = 1
>
>Define T26 integer size 1 = 26
>
>Define CNTRL_A character size 1 = characters ( T1)
>
>Define CNTRL_Z character size 1 = characters ( T26 )
>
>Procedure input fff
>begin
> if CNTRL_Z = FIELDTEXT[1:1]
> THEN INFO "CONTROL Z entered"
>end
>
>I would avoid using control characters because a lot them are used for line
>editing.
>
> Interestingly, Microsoft gets in before QUICK if you are using
> International English or one of the national keyboard maps.
> Microsoft translates your keystokes ( usually a dead key for the accent
>and a vowel )
> into a single character.
>
> But the other ways of creating non-English characters are
>not available to the QUICK user because the translation of multiple
>characters to one
>is done in the input buffer. But QUICK has already read the first character
>before the translation
>occurs.
>.
>Regards,
>Peter
>
>
>
>>Moving right ahead with our migration from the HP3000 to Windows, we are
>>now coming to grips with the fact that the Windows Console does not support
>>function key labels. Really a shame as this greatly reduces the practical
>>use of function keys. We did some fairly tricky things, especially in DATA
>>context, that we cannot re-produce. We did use several levels of function
>>keys in our largest (read that "most important") screens.
>>
>>We have designed a new means to navigate through our application using more
>>menus, more Designer Procedures, more input from the Action box, more use
>>of Info messages, and "fixed" function keys F1 - F12. We have all 12
>>working without relying on Shift or Alt or Ctl by modifying the TIC file.
>>
>>Works OK, though it took "more" of practically everything, but still not as
>>smooth (easy, intuitive, slick, better - fill in your favorite ) as using
>>function keys and labels. Oh well.
>>
>>That said, has anyone else dealt with this issue? Does anyone have any
>>ideas? The latest New Features manual mentions connecting to the Windows
>>Console via a terminal emulator - has anyone ever done this? How? Not
>>sure we would go this route, but we are curious.
>>
>>Has anyone ever "trapped" a key being pressed, like <F1>, or Ctl W? So we
>>could do something like : IF FIELDTEXT = <F1> (Ctl W, whatever) THEN RUN
>>SOME DESIGNER OR INTERNAL PROCEDURE ... If we could get this to work we
>>could get a little of our "smooth" back.
>>
>>Too bad you can't run Designer procedures in DATA context.
>>
>> All ideas are welcome. Anyone who wants to talk about it feel free to
>>give me a call - (972) 442-9718. If you are going through the same
>>migration I can tell you what NOT to do.
>>
>>Thanks.
>>
>>Don Baird
>>EnCore Systems
>>
>>
>>
>
>_________________________________________________________________
>Designer Mail isn't just fun to send, it's fun to receive. Use special
>stationery, fonts and colors.
>http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=htt
>p://hotmail.com/enca&HL=Market_MSNIS_Taglines
> Start enjoying all the benefits of MSNŽ Premium right now and get the
>first two months FREE*.
>
>
>
>--__--__--
>
>--
>= = = = = = = = = = = = = = = = = = = = = = = = = = = =
>Mailing list: powerh-l@lists.sowder.com
>Subscribe: "subscribe" in message body to powerh-l-request@lists.sowder.com
>Unsubscribe: "unsubscribe <password>" in message body to
>powerh-l-request@lists.sowder.com
>http://lists.sowder.com/mailman/listinfo/powerh-l
>This list is closed, thus to post to the list you must be a subscriber.
>
>
>End of powerh-l Digest
>
>
>