Quick screen auto-find

[Jim Hamer]

Chris,

We have crossed that bridge as well. 

We wrote an Inquiry subsystem that had a Parent screen and 40 sub-inquiry
screens. We carry the key data from the parent screen down to any of the
sub-inquiry screens and then the user can call up a new record while on a
sub-inquiry screen. (We also passed the new key back up to the Parent.) We
solved the problem the way you have described by writing Path and Find
procedures. These were put into a USE file and in most cases the
sub-inquiry screen would reference the USE file and following that have the
additional files (Detail or Secondary) that were required. I confess that
we had to Get these additional files by coding the Get in the Detail Find
procedure.

All the screens in the subsystem were designed to have the same 'look and
feel'. Each screen had the same data at the top of each screen. This was
the key data from the Primary record. This lead us to have 3 USE files. The
first file contained the Primary file and Access statements, along with the
necessary Temps and Defines and the Reference files. The second USE file
contained the Field statements for the layout of the key data. There are 6
lines of key data. The last USE file contained the Path, Find and Exit
(where we set the variable to pass back up the key value) procedures.

Once the USE files were set up, creating the subsystem was fairly simple.

Jim


Jim Hamer                                      Contract System Analyst
Dairy Farmers of Ontario                       (416) 489-3298
Information Systems Division                   hamer@inforamp.net
(905) 821-8970                                 Toronto, Ontario, Canada
jhamer@milk.org
http://www.inforamp.net/~hamer/
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
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.