Tom Burton has been using FileMaker and FileMaker Pro for approximately 10 years. FileMaker Pro is an extremely powerful and flexible relational database program. It is also totally cross-platform, so a database can be used by a mix of Windows and Mac users.

Tom's philosophy is that the database is not an end itself. It must serve a purpose; the purpose and the people using the database (both using it on a day to day basis and using the reports it produces) should determine the database's structure and user interface.

Ideally, a database will facilitate extracting useful information out of a collection of data. As an example, a database of customers and purchases should provide information as to the highest selling products or lines, and the customers that make the most (and/or highest dollar value) purchases. This is valuable information that can make the company's marketing efforts most effective.

The user interface should be as intuitive as possible, and should reduce or ideally eliminate entry errors. The user interface should make sense to the people who will be using it, otherwise they will resist using the database. The database should help them do their job.

FileMaker Pro allows creation of databases from the simple (such as a Neighborhood Watch roster) to a level of complexity limited only by the desires of the client and the ability of the developer.

For Micropolis Corporation, a manufacturer of high-performance disk drives, Tom developed and maintained databases for tracking initial purchases and add-on modules for expandable storage subsystems. This proved very useful for Micropolis' sales force and for distributors representing Micropolis, allowing them to see who purchased what and when.

He also created a database that tracked advertising and trade show leads, which facilitated follow-up. Prior to that, follow-up was at best random and inconsistent.

For Nbase-Xyplex, a manufacturer of media converters for the fiber optic network infrastructure market, Tom created a standalone FileMaker Pro product selector database, called the Fiber Driver Configurator. Nbase's product line was extensive, with over 350 different modules that perform multiple functions; the sales force and Nbase's customers had trouble determining which module would fit their particular need (or combination of needs). The database took into account the functions, and simply allows the user to enter whatever requirements they know. It returned detailed information on all of the modules that met their criteria.

Since it was a standalone application, the user does not need to have the FileMaker Pro application on their computer, nor need to know anything about FileMaker Pro (or, for that matter, either the FileMaker Pro or Windows menus or commands); all operation of the database is via buttons, eliminating user error.

Here's the selection screen:

For Gourmet West, a wholesale broker in the gift and home décor industry, Tom created an evolving FileMaker Pro database. Initially, it was simply a customer and prospect tracking system. Then it grew to include Order Processing, crediting sales to the appropriate Sales Representative (and allocating that rep's portion of the sales commission), reconciling commissions owed to Gourmet West, tracking partial shipments/payments, maintaining a powerful yet easy to use "To Do" list, and including customer credit information with orders when desired. Typical reports for this database are Sales Per Month by Sales Representative, and Total Sales Per Month Compared with Last Year.

He developed a similar database for Hennessy & Company, another wholesale broker (that specializes in unique home, office, and gift items). This one was customized for Hennessy's specific requirements.