Purpose §

Defines an administrator-defined SQL Server or SQLite database view.

Where used §

ODBC database connections.

Data fields §

Name §

This is the view name that is referenced by ODBC clients. PDXpert view names must always begin with the letters My... as in, say, MyReleasedParts. The name must conform to the executing database engine's (Microsoft SQL Server or SQLite) guidelines.

The safest names for all ODBC clients are those that contain only ANSI alphanumeric and underscore ("_") characters, and are not SQL reserved keywords.

It's often useful to apply a suffix to views that are compatible with only one engine, such as MyItemsSQLite or MyItemsMSSQL. A view compatible with both databases wouldn't have a suffix: MyItems.

Description §
This describes the view and its purpose.
SQL SELECT statement §

This is the SQL SELECT statement that produces the view.

  • When the ODBC client connects to the server-side SQL Server database, or the optional client-side SQL Server LocalDB, the SELECT statement must conform to SQL Server syntax.
  • For ODBC clients connecting to the client-side SQLite database pdxpert.db, the SELECT statement must (a) conform to SQLite syntax, and (b) select data only from the set of SQLite-compatible public views.

    Each time the PDXpert client starts, the client-side views are updated from the server. Minimizing the number of views, and custom attributes within each view, reduces the time required for the client to start.

Active: users can select §
Default member of collection §
Permanent member of collection §
For a description of these checkboxes, see the Collections reference > Managing collections help topic.

Setup suggestions §

A SQL Server administrator-defined view must always be based on PDXpert's public views.

For important information about creating views, refer to the How to report, import & export > Viewing & exporting via ODBC help topic.

Any change to a view, or to custom attributes that appear in a view, can affect the local views database. Before you change a view and before you add, remove or rename custom attributes used within a view, all other users should exit PDXpert and all ODBC applications that use local views. After making your changes, users should start the PDXpert client before resuming work with the ODBC application.

After upgrading to a new PDXpert release, always test your views for proper operation.

A view's SQL is not visible to PDXpert's upgrade process. A view may require some modifications to maintain compatibility with PDXpert upgrades.

Views included with your PDXpert system are provided for demonstration purposes, and may not be compatible with future PDXpert releases.


Learn More
Help Guide Contents [PDF]