Changing requested values in quick

[Jones Allen (Van)]

Yes, but Powerhouse's default editing for dates is applied between the
input and edit procedures.  Since the format is YYMMDD, the edit fails
because fieldtext is > 6 long.

in response to Hans Hendriks who suggested defining a century included
temp date and requesting it, rather than our existing date field:
All our dates are already century included, but our format is not.
However, your idea may be our only reasonable alternative.  In that
case, we would change our existing screen field formats to be YYYYMMDD
rather than introduce new items.  We'd  ike to avoid changing our screen
layouts, however, because that requires changes to our PHwin
repositories, more overhead, etc.  Also, we have tried to avoid
hard-coding date formats in programs because it  removes the flexibility
of using the dictionary default format.  Alternatively, we could define
new temps that are used for lookup only, and assign them values in the
postpath based on what the user has entered, but then we'd have to code
access statements instead of letting Powerhouse generate them.


> -----Original Message-----
> From:	dmaclary@wellmanage.com [SMTP:dmaclary@wellmanage.com]
> Sent:	Thursday, June 25, 1998 12:53 PM
> To:	allen.jones@artioslink.com
> Subject:	RE: Changing requested values in quick
> 
> Have you tried adding the century in the input procedure?  Here's a
> do-it-yourself approach...
> 
> IF FIELDTEXT is 6 chars and the first 2 positions are, say, 60 or
> higher,
> then
> add "19" to the beginning of FIELDTEXT, else add "20".
> 
> Regards,
> David Maclary
> 
> > ----------
> > From: 	Jones Allen (Van)[SMTP:allen.jones@artioslink.com]
> > Sent: 	Thursday, June 25, 1998 2:26 PM
> > To: 	'powerh-l@lists.swau.edu'
> > Subject: 	Changing requested values in quick
> > 
> > It seems that Powerhouse stores requested values in a "search" or
> > "request" buffer that is immune to initializations that happen at
> the
> > start of the find process.  We would like to change requested values
> in
> > the postpath procedure.
> > 
> > For example, during a find, the user enters "991024" (yes this is a
> Y2K
> > work around).  Our default century in the dictionary is "20" and the
> > date format is "YYMMDD".  Powerhouse applies the default century and
> > stores "20991024" in the request buffer.  We would like to intercept
> > this during the postpath and change it to "19991024". 
> > 
> > [Some background:  Setting the default century to 20 lets us keep
> our
> > default date format as YYMMDD and still allows 20000229 as a valid
> date.
> > We have code in the edit procedures to change the century according
> to
> > the year, but the edit procedure is not run in a request verb.  We
> can't
> > apply the century switch in the input procedure because Powerhouse
> does
> > the automatic date edit and applies the default date format between
> the
> > input and edit procedures.  Ideally, we should use the Y2K versions
> of
> > Powerhouse, but when we tried "ph8.13c" and "d" on our HP-UX system
> we
> > discovered other problems with them, so we're still on 7.33d3.]
> > 
> > Thanks in advance for any help you can give.
> > 
> > Allen Jones
> > Artios Canada
> > = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> = = =
> > =
> > Subscribe: "subscribe powerh-l" in message body to
> > majordomo@lists.swau.edu
> > Unsubscribe: "unsubscribe powerh-l" in message to
> majordomo@lists.swau.edu
> > powerh-l@lists.swau.edu is gatewayed one-way to
> bit.listserv.powerh-l
> > This list is closed, thus to post to the list, you must be a
> subscriber.
> > 
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
powerh-l@lists.swau.edu is gatewayed one-way to bit.listserv.powerh-l
This list is closed, thus to post to the list, you must be a subscriber.