Valid Uses for the View Parameters

Last reviewed: September 20, 1995
Article ID: Q136940
The information in this article applies to:
  • Microsoft Visual FoxPro for Windows, version 3.0

SUMMARY

This article explains how to use the "?" character to build a parameterized view. In particular, it addresses the issue of the location of the "?" in the WHERE clause, and of using macro substitution with parameterized views.

MORE INFORMATION

View parameters provide a mechanism for value substitution, not macro substitution.

In the View Designer, you can specify parameters on the right side of the WHERE clause (and the HAVING clause). However, parameters are still legal on the left side of the WHERE clause.

Both of the following commands create a valid parameterized SQL view:

   CREATE SQL VIEW viewname AS SELECT * FROM tablename;
      WHERE field1 = ?param1

   -or-

   CREATE SQL VIEW viewname AS SELECT * FROM tablename;
      WHERE ?param1 = view1

In both cases, when the VIEWNAME view is opened, the user is prompted for a value for PARAM1, which is then used in the WHERE clause.

An example of macro substitution in the left side of the clause would be if the following view allowed the user to supply a field name for FIELDPARAM rather than just a value.

   CREATE SQL VIEW viewname AS SELECT * FROM tablename;
      WHERE ?fieldparam = ?param1

Although this is a valid view, the effect is to compare the value entered for ?FIELDPARAM with that entered for PARAM1 for all records. The macro substitution does not occur.


Additional reference words: 3.00 VFoxWin question mark parameterized
view database
KBCategory: kbprg
KBSubcategory: FxprgSql


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: September 20, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.