All documentation

InfoQuest Client

Use InfoQuest Client Manager to sign on, design and run requests, schedule reports, and download results to the PC.

Last updated April 29, 2010

What InfoQuest Client does

InfoQuest Client puts a Windows GUI on the InfoQuest server. Users sign on, pick an application and view, build a request with point-and-click data selection, and either run it now, schedule it for later, or rerun an existing request. Output can be downloaded to the PC and opened in a built-in viewer.

Sign-on and profiles

  • User Profiles — choose an available profile, sign-on script directory, and host route
  • Sign On — User Id, Department, Password, and Host Connection Path
  • InfoQuest Client Manager Configure — default download directory, view/parameter directory, uppercase enforcement, and option to reuse the InfoQuest user/password as the system sign-on
  • Enter New InfoQuest Password — change the password from inside the client

Creating a request

  1. Select an application, then a view
  2. Choose how to create the request and the output type (report, file, viewer)
  3. Develop the request — pick fields, build selection criteria, choose subtotals and sorting
  4. Name and save the request, or run it immediately
  5. Process the request through Q-LINK and download the result

Data selection

Selection criteria are built visually with operator + value expressions joined by AND/OR. Common patterns include date-range filtering with the *DATEyyyy-mm-dd literal, alpha-literal matching, and conditional operators with the SET command for derived values.

START DATE <= *DATE1993-12-31 AND
END DATE   >= *DATE1993-01-01

IF COMP TYPE = 'POOL'
  SET &COMP TYPE TYPE& = 'Pool Company'
ENDIF

Scheduling and rerunning

  • Schedule a request with Start at Time Specified for off-hours runs
  • Rerun Existing — pick a saved request from the list
  • Remove a request from automatic scheduling when no longer needed
  • Subtotal Break, Min/Max, and grouping options carry across reruns
Note: Sign-on script directories are per-profile — keep separate scripts for production vs. test connections.