home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!spool.mu.edu!darwin.sura.net!gatech!concert!rutgers!cmcl2!adm!smoke!brl.mil!fsbrn
- From: fsbrn@brl.mil (Ferd S. Brundick)
- Newsgroups: comp.databases
- Subject: Re: Paradox bug/feature in query form? (3.5)
- Message-ID: <19532@smoke.brl.mil>
- Date: 8 Jan 93 15:13:11 GMT
- References: <1993Jan7.183802.12921@blaze.cs.jhu.edu>
- Sender: news@smoke.brl.mil
- Reply-To: fsbrn@brl.mil
- Organization: Army Research Laboratory
- Lines: 38
-
- In article <1993Jan7.183802.12921@blaze.cs.jhu.edu>, mancini@circle.cs.jhu.edu (Todd A. Mancini) writes:
- |>
- |> Here's something I noticed in PDOX35, but have not yet tested in PDOX40...
- |>
- |> When I use a variable name in a query form from PAL (by using the
- |> ~variablename) notation, if the variable contains any wildcards they are
- |> ignored. Is this documented?
-
- Yes, it is documented, or at least I remember seeing the solution in
- an example in the Query portion of the User's Guide. Put the
- wildcards outside the variable like this:
-
- LNAME = "M"
-
- query
-
- cust | last_name | first_name |
- | check ~LNAME.. | check |
- | | |
-
- endquery
-
- DO_IT!
-
- It is the same as the literal
-
- cust | last_name | first_name |
- | check M.. | check |
-
- In my application the user always wants the wildcards, so I didn't
- have to worry about allowing him to type them in. My app is written
- in 3.5 and behaves the same under 4.0 Runtime in compatibility mode.
- I haven't tested it in 4.0 standard mode yet.
-
- dsw, fferd
- Fred S. Brundick
- USARL, APG, MD.
- <fsbrn@brl.mil>
-