PH 8.19c2 Field Duplicate in Quick
John MacLerran
macljohn@isu.edu
Wed, 10 Mar 1999 09:36:25 -0700
The wierdness continues...
I tried changing the format to YYMMDD, and that didn't change the symptoms, so I
changed it back to MMDDYY for the tests outlined below.
-- Entered 03/10/99 (with slashes) the screen duplicated the field, but the
value displayed was 03/10/91 -- in the database, it is 03/10/0991.
-- Entered 031099 (w/o slashes). The screen did not duplicate and gave an error
message that the field must be a date.
-- Entered 03101999 (w/o slashes). The screen did not duplicate and gave an
error message that the field must be a date.
-- Entered 03/10/1999 (w/slashes). The screen duplicated the field, but the
value displayed was 03/10/97 -- in the database, it is 03/10/0197
However, if I change the date format on the field in Qdesign to include the
century (MMDDYYYY), then everything works correctly. I can enter a date, with or
without slashes, and with or without the century, and everything duplicates
correctly and as it should. Basically, this makes the output format correspond
to the implied input format that Allow Century uses -- as Bob noted below.
So the question remains. How do I get a date field to duplicate correctly with
Allow Century and a format of MMDDYY?
"Deskin, Bob" wrote:
> As far as I can tell, QUICK is behaving correctly (well almost - see below).
> What's catching you is the new feature ALLOW CENTURY. Basically what this
> does is allow you to enter the century into a century included date field
> that has a century excluded date format. It does this by making the field a
> scrolling field AND changing the input format to a century included one. In
> your case, your date format is MMDDYY. This remains the output format. But
> with ALLOW CENTURY the input format becomes MMDDYYYY. Now we all know that
> PowerHouse accepts dates with or without a separator as long as it can tell
> which piece is the month, day, and year. In the case of entering 030399,
> PowerHouse doesn't assume the each piece is 2 digits (we can argue whether
> that's intelligent or not at a later time). This means that you need the
> separators. Keep in mind that this is exactly the same behavior as if you
> had a date format of MMDDYYYY right on the field statement.
>
> As for the strange value being inserted, check if the actual value on file
> and in the buffers is correct. There may be a display problem I'm not aware
> of.
>
> Bob Deskin
> Senior Product Advisor bob.deskin@cognos.com
> Cognos Inc. (613) 738-1338 ext 4205 FAX: (613) 228-3149
> 3755 Riverside Drive P.O. Box 9707 Stn. T, Ottawa ON K1G 4K9 CANADA
>
> -----Original Message-----
> From: John MacLerran [mailto:macljohn@isu.edu]
> Sent: Tuesday, March 09, 1999 7:00 PM
> To: powerh-l@lists.swau.edu
> Subject: PH 8.19c2 Field Duplicate in Quick
>
> Hi Everyone,
>
> I'm having a problem with field duplicating in quick (HP3000, v
> 8.19c2). I have a screen with the following:
>
> FILE TIME-SHEET PRIMARY OCCURS 8
> ACCESS VIA EMP-ID REQUEST EMP-ID OF TIME-SHEET
> ACCESS VIA PROJECT-NBR REQUEST PROJECT-NBR OF TIME-SHEET
>
> <snip>
> CLUSTER OCCURS WITH TIME-SHEET
> ;
> FIELD PROJECT-NBR OF TIME-SHEET REQ &
> LOOKUP ON PROJECT MESSAGE "This project number does not exist"
> FIELD JOB-CODE OF TIME-SHEET DEF 'O' DUP
> FIELD DATE-T OF TIME-SHEET &
> default SYSDATE &
> duplicate &
> format MMDDYY separator '/' &
> allow century
> CLUSTER
> <snip>
>
> The Job-Code field is correctly duplicating from one occurrence of the
> cluster to the next, but the field DATE-T is not. If I enter 030999 for
> a date, the screen accepts it and formats it as "03/03/99", which is
> correct. On the next occurrence, if I press return to accept the
> duplicate process, I get an error that the field must be a date. I can't
> even type in the underscore ('_') to force duplication. There are no
> user-defined procedures associated with either of the fields.
>
> Now for the _really_ wierd part. If I type in the date with slashes
> (03/09/99), the screen accepts it, and on the next occurrence, I don't
> get the error that the field must be a date, but the value that is
> inserted into the field by Quick is 03/09/91!
>
> Can anyone tell me why this is happening, and what to do to correct it?
> Or, has anyone heard of this being a problem with 8.19c2? If I need to
> request 8.19c4, I will, but I'd like to know if this is a known issue
> and if it's fixed in c4.
>
> Thanks!
> ----------------------------------------------------------------------
> John MacLerran
> IT Systems Analyst email: macljohn@isu.edu
> Idaho State University V(208) 236-2872
> http://www.isu.edu/~macljohn F(208) 236-3673
> ----------------------------------------------------------------------
>
> = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> 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.
--
----------------------------------------------------------------------
John MacLerran
IT Systems Analyst email: macljohn@isu.edu
Idaho State University V(208) 236-2872
http://www.isu.edu/~macljohn F(208) 236-3673
----------------------------------------------------------------------
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
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.