Counter

[Neil Harvey]

Elisabeth's last point is valid - sooner or later, they will want this
feature (pesky users!).
If not, use date/time as a sort key - that way, you get an automatic
time stamp on the notes.

Neil


-----Original Message-----
From: elis [mailto:elisabeth.corsten@ec-datentechnik.de]
Sent: Sunday, March 14, 1999 10:44 AM
To: powerh-l@lists.swau.edu
Subject: AW: Counter


Try the following:

- declare the NOTES file a second time as alias A-NOTES designer
- declare a temporary field T-COUNTER
- whenever the NOTES are displayed for the first time, do a GET on
A-NOTES with a WHILE RETRIEVING loop
- LET T-COUNTER = COUNTER-NO (returns the value of the last issued
counter)
- in FIELD processing the NOTES text field (if newrecord), LET
COUNTER-NO = T-COUNTER + 1 and LET T-COUNTER = T-COUNTER + 1.

BTHW, why do you want the counter numbers to be invisible? Judging from
my experience it doesn't take the users long to decide that they want to
be able to re-arrange the display sequence of "their" text notes...

Good luck
Elisabeth

> ----------
> Von: 	Tumulties@aol.com[SMTP:Tumulties@aol.com]
> Gesendet: 	Sonntag, 14. März 1999 06:23
> An: 	powerh-l@lists.swau.edu
> Betreff: 	Counter
> 
> I have a Quick screen which allows the user to enter notes (text field
> of 50
> bytes) on a customer.  In the Customer notes dataset I have a sequence
> field
> (sort item) in addition to the 50 byte text field, so the notes can
> always be
> retrieved in the order they were entered.  I don't want this sequence
> field to
> be displayed on the screen, I simply want the user to enter the notes
> and
> automatically populate the sequence field (behind the scenes if you
> will).  I
> have tried defining a counter field and incrementing it by one, and
> then in
> the cluster command setting the field  silent value counter, but this
> didn't
> work.  
> 
> How does one populate a field with an incremental value without having
> a user
> having to enter the value on the screen?  I have scoured the Qdesign
> Procedural and statement reference manuals for a clue, but no luck so
> far!  
> = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> = = =
> 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.
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
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.