home *** CD-ROM | disk | FTP | other *** search
- This Zip Archive consists of the two screen files describing two
- techniques to limit the display and editing of records in a table. This
- is a similar to the "View" concept in SQL.
-
- The first example is called SetFltr.Fsl. This shows how to restrict
- your view of records by using the SetFilter method on a Secondary (or
- probably Primary) Index. By pushing the proper PushButton, it limits
- the set of records to those who live in the state of "CA".
-
- The second example (Qry.fsl) uses a Query as part of the basis for
- the building of a Form. In this Query, the Key field is checkmarked.
- Then other related fields are tied to this field. Any of the fields
- with the exception of the Query field can be changed. This is a good
- way to limit the records to be edited. Since the Query is only
- returning the set of key field entries that match the Query criteria,
- it executes fairly quickly.
-
- The caveats for Qry.fsl are as follows:
-
- 1. Once all of the linkages of the tables are set up, you'll need
- to go into the Data Model and reset the read-only attributes.
- "Right Click" on the Tables in the data model.
-
- 2. Unfortunately, since these tables ARE look-up tables, you cannot
- perform searches for data elements like you usually can unless
- you write some ObjectPAL. What you would have to do is trap the
- Locate Function, check for the search being on the key field
- (allowing it to go through if it is), else open the table using
- a TCursor and search for the requested data in the table. Once
- found, you'll need to get the key value from that record and
- search in answer table for that key value.
-