Case Study One
Client: A summer and winter camp for children in Colorado; camp’s participants come from all over the world.
Problem Scope: The camp admits hundreds of children each year from a pool many times larger; many of the attending kids are “repeats.” Information about the children is captured and used during the application process. The camp also encourages sibling participation and program development over several years. The camped needed to track individuals as a multi-year package, remembering sessions, achievements and co-attendees. Data about camp counselors needed to include previous attendance and camp experience. Parent data needed to include how parents have been involved with the camp (e.g. volunteering, fundraising, board and advisory councils).
Solution: Database coordinates information about parents, children, volunteers (of all ages), board and council members, vendors, donors, and integrates the data to produce digestible, useful information for camp directors. Two years ago, a data bridge was added to the accounting system. Recent modules allow a database browser to see related, relevant photo images. Camp merchandise sold on premises and via the web is inventory-controlled by an independent module.
Technical Details: Medium size, multi-user networked environment, several dozen tables of data, hundreds of queries, forms and reports. Macros and code modules are generally hidden from the casual user. Financial information is stored and used in an external-off-the-shelf accounting system but is exported to the database, modified as needed and re-imported back to the accounting system; photo images are stored and manipulated by an external off-the-shelf photo imaging software but images are visible and printable inside the database forms and reports.

Case Study Two
Client: Small engineering services and construction company that builds nurse call systems and related hospital environment communication technologies.
Problem Scope: Client builds engineering subsystems into new and existing healthcare facilities. They go through the process of responding to an RFP, bid, design, build, implement, test, install and maintain engineering systems. Database needed to coordinate information about a project, breaking it down into jobs with a well-defined start and finish. Since the client buys subsystems from manufacturers and integrates them into their own construction, data management needed to include the details of purchase, dollars, delivery, transshipment, installation, labor allocation, billing of their clients and inventory control.
Solution: Database handles all data and includes a custom interface to client’s Peachtree Accounting package.
Technical Details: Medium size, multiple networks, simultaneous users, several dozen tables of data, hundreds of queries, forms and reports. Macros and code modules are generally hidden from the casual user.

Case Study Three
Client: Public sector utility with three nuclear power plant units
Problem Scope: Client needed a database to handle extremely technical engineering information, which is highly organized and follows a rigorous engineering discipline.
Solution: With the consultation of a subject matter expert, created an island of related data records stretching across 14 data tables. Records describe the maintenance engineering details of large and complex power plant components. Database allows client to copy component data into another island with a similar data structure while maintaining the data integrity and remembering the source of the information. This function retains the textbook specs in the original island, while adjusting the copy for practical realities, saving the client hundreds of thousands of dollars in input time and errors correction.
Technical Details:  Large size, multi-user networked and secured environment. The database is about 250 megabytes and contains hundreds of thousands of records. The total number of software objects (tables, queries, forms, reports, macros and modules) is in the several hundreds. This database easily interfaces with other pre-existing Oracle databases, spreadsheets and Word documents.

Case Study Four
Client: Private clinician with a local medical practice.
Problem Scope: Client looked at existing off-the-shelf medical packages and concluded they cost too much to customize for their unique medical discipline. Client’s clinicians travel across the metro area and see patients in a number of neighborhood facilities.
Solution: Database designed to work from remote locations. Database stores appointments (in a calendar book style seen in doctors’ offices) for as many as six practitioners. It tracks patients’ medical details, insurance and the course of treatment. In addition to the large, full screen appointment book display breaking the day down into 30-minute segments, database can show the clinician photographs of the patients from each visit along with supporting textual data.

Database Features

Listed are features of our custom builds gathered from various projects, demonstrating the scope of our creativity and sensitivity to client needs.

  1. Zip Codes: Many of our clients have a need to mail information to their clients and prospects. We have mail handling code that can use data from existing databases. This feature remembers what was sent to whom and supports zip code-based operations.

  2. Map Info: Zip code-based data from existing records can be integrated with map information to show the database operator a visual of where his existing data is pointing.

  3. Size Issues: One of our databases pushes the limits of Microsoft Access by being just under the limit of two gigabytes of data in the “home” database. By taking advantage of the external data table link features, this database is currently managing four gigabytes of data from one portal and is growing. There is one parent table with three million records, and a related child table that exceeds 40 million records; the whole integrated package runs in Microsoft Access version 2003.

  4. Photo Handling: Database software modules display and print images from inside the database; the images are physically resident outside the database in a well-organized image directory with subdirectories.

  5. Remote Operations: Trouble-free access to your data is available now.

  6. Accounting Packages: Our databases integrate with the two most common small business accounting packages: Peachtree and Quicken. We can take your accounting data and tie it to your other data. This automation may save you many manual steps and eliminate errors.