Databases

A database can be any collection of records or files related to a common subject. In simplest terms, a single spreadsheet of telephone numbers is a database.

Do you need a database?

There may not be an easy answer. You need a relational database when you need to extract repetitive information from mountains of information.

But what about the other end of the spectrum?

Answering "yes" to two or three of these questions indicates you may soon need a database.

• Do you keep related tabular information in several spreadsheets?
• Do you have several thousand lines, or several hundred columns, of information?
• Do you use spreadsheets with much information repeated from row to row or column to column?
• Do you store similar information in two or more formats?
• Do you search spreadsheets for useful information with several successive search iterations?
• Do you ever extract information from one program, and then enter it into another for a limited purpose?
• Do you have information in such forms that only one person in your organization can find or manipulate?

Spreadsheet programs like Microsoft Excel and Lotus 1-2-3 can handle multiple spreadsheets. And advanced users can build complicated applications that can use lookup queries and macros to pull in diverse information.

There is a point, however, when using a database becomes a better choice. Deciding to switch to database applications is often difficult because database programs like Access and Oracle are so intimidating. Consequently, the move to relational databases is often delayed.

We can help!

We like complicated, diverse information. And we like medium-sized problems. (We define "medium" as being between a hundred thousand and a half-million lines of information.)

We work with Microsoft Access and are experienced with entering and extracting information in many different formats.

To make those databases easier to use, we generally build "front-ends" to allow you to find and enter data in forms.

Sometimes, search routines become more complicated than even Access can handle through its robust query language. In those instances, we use subcontractors to write custom Visual Basic code that is then inserted into Access databases.

Maybe you don't need a database

In some cases, you may not really need a full-blown Access database.

We have substantial experience working with spreadsheets, reaching back to the first version of Lotus 1-2-3 in the 1980s. We use spreadsheets on a daily basis and may already have solved the problem you need help with.

Give us a call

Admittedly, we may not be able to solve your problem. But we will try to dispell some of the mystery and try to point you in the right direction.

While you're here, examine some of our examples and see if any of your problems resemble the ones we have already solved.