Working with your data

Graf-FX will work with any data that Microsoft Access understands. The product has been setup so that all the queries that are shown are readonly and the grafs also protect the data. This includes

Microsoft FoxPro, dBASE, Paradox, SQL tables and data from programs and databases that support the ODBC protocol, Microsoft Excel spreadsheets and delimited and fixed width text files. Files can be imported on a regular basis from other formats such as Lotus and any program that can output text files.

The following help shows the steps to link to a Paradox file.

You can import or link Paradox or Paradox for Windows tables (versions 3.x, 4.x, and 5.0).
Switch to the Database window for the open database. This is the first toolbar icon and the or you can use the link table option directly using the second on the graf-fx toolbar.
Using the menus, to import tables, on the File menu, point to Get External Data, and then click Import.
To link tables, on the File menu, point to Get External Data, and then click Link.
In the Import (or Link) dialog box, in the Files Of Type box, select Paradox (*.db).
Click the arrow to the right of the Look In box, select the drive and folder where the .db file is located, and then double-click its icon.
If you want to import or link another Paradox table, repeat these steps. When you have finished importing or linking, click Close.

You will use a similar sequence to link to the other database types. If you want to find out how to setup ODBC, point your internet browser to http://www.gr-fx.com/odbc/ODBC.htm

Now you can drilldown on the table that you have linked to.

If you want to subset your data or join tables together using common relationships, you can create a query using Microsoft Access query builder wizard as follows

Create a simple select query with a wizard
Switch to the Database window using the Graf-FX Toolbar
In the Database window, click the Queries tab, and then click New.
In the New Query dialog box, click Simple Query Wizard, and then click OK.
Follow the directions in the wizard dialog boxes. In the last dialog box, you can choose to run the query or see the query's structure in Design view.

If the resulting query isn't exactly what you want, you can rerun the wizard or change the query in Design view.

Bringing together data from more than one table or query in a query

The power of queries lies in being able to bring together information from more than one table or query. For example, you might want to view customer information with the orders they placed. To see this information, you need data from the Customers and Orders tables.

When you add more than one table or query to a query, you need to make sure their field lists are joined to each other with a join line so that Microsoft Access knows how to connect the information.

Then, when you add fields from both tables or queries to the design grid in query Design view, the default join tells the query to check for matching values in the join fields. (This is called an "inner join" in database terminology.) When it finds matches, it combines those two records and displays them as one record in the query's results. If one table or query doesn't have a matching record in the other table or query, neither record appears in the query's results. If you want the query to select all the records from one table or query whether or not it has matching records in the other table or query, you can change the join type. For examples of different join types and how they affect query results, click .

Note: If tables in a query aren't joined to one another, either directly or indirectly, Microsoft Access doesn't know which records are associated with which, so it displays every combination of records (called a "cross-product" or "Cartesian product") between the two tables. Therefore, if each table had 10 records in it, the query's results will contain 100 records (10X10). It also means the query might take a long time to run and ultimately might produce less meaningful results.

Whilst this does not explain the science of querying data to you, the following basic rules apply to queries that can be utilised in the Launchpad Drilldown form.
Firstly the query must be a select query that retrieves data (not an action query such as an update, insert, delete or make table query.
Any query that is viewed within the graf-fx system will only show readonly results rather than the default access option of read/write if possible.
You can embed the powerful iif statements in queries.
You can embed any Access function, your own function or a Graf-FX library function into your query
It is recommended giving the column a useful alias (name) when using iif or other functions to make it more understandable in the drilldown analysis.
When giving tables and queries new names, avoid using names with spaces and keep the names short but informative. The description property can be used to provide more information to the user.

Now that you have added a new linked table or query, you will find that they will instantly appear in the launchpad like the example as follows. Here "aNewTable" and "aNewQuery" were added to the graf-fx database.

Note that all the graf-fx example tables and queries have been saved with a "z" prefix so that they are easy to separate from the users real information.

.