About Lea Database Design

Lea Database Design is focused on creating highly-customized, user-friendly and affordable data management solutions for your business or organization. We offer one-on-one attention and solutions designed especially for you. At Lea Database Design, we want to work with you to create your industry-specific data in a well-organized, easy to access system; a system that will grow as your business grows.

Do you have Excel and Word files full of customer-related information that is becoming difficult to manage, making it nearly impossible to find what you're looking for? Let us build a customized database putting that information at your finger-tips; a database that will grow with your business and will help you coordinate your activities, saving you valuable time and increasing your efficiency. We'll custom-build a database to support and coordinate your activities, saving you valuable time and increasing your efficiency as you grow.

You may have an existing database that just isn't working. We can fix it! We can redesign your applications, creating the useful management tool you need to keep track of all of your data.

Are you using QuickBooks for your basic accounting needs but you want to do more with your data? Smallbusiness.chron.com says, "QuickBooks is a dedicated accounting program, while Microsoft Access is a broader database management system. QuickBooks handles customer and inventory data, but you may want to migrate this data to Access for further analysis. Access can perform more sophisticated queries than QuickBooks, and its reports allow you more flexibility." With over 20 years of experience, MS Access databases are our specialty!

Why choose MS Access versus Excel

Microsoft article

  • Do you need to help users enter data? For example, some users find it hard to enter data in a grid of cells. With Access, you can work around that problem by creating data entry forms that make it easier to enter data accurately.
  • Do your users need reports? With Access, you can create reports that users can run at any time.
  • Access is also a better choice when you need to have multiple users working on the data at the same time. Several users can work on the same data, because Access locks a record only while a user changes it. You can share an Excel workbook with several users, but the process works best when users change data in Excel at separate times.
  • If you need to connect to several data sources and edit the data directly in those sources, then Access is your choice. You can view external data with Excel, but you can't change that data.
  • Do you need to store and manage your data, or do you need to analyze that data? If storage is your primary goal, then use Access.
  • Do you have a lot of data? For example, is your Excel worksheet so large that it's hard to use? If so, even if you have flat data, Access can make your information easier to find.
  • And finally, a relational structure helps keep your information accurate, because you can prevent users from entering data in the wrong table.

Read more

Excel Vs. Access – Can A Spreadsheet Replace A Database?


Or should you be using both? Access and Excel both feature data filtering, collation and querying, but which program is suited to your work requirements, and how do you get the best of both worlds?

Understanding What Each Tool Is For

Access versus Excel

Read more

Related article from Microsoft

Using Access to build a front end for SQL Server

Tech Republic, Susan Harkins

What are the advantages of using Access as the front end to a SQL Server database? For starters, it's likely that your client's users will be more familiar with it, and it's relatively easy to put in place.

Knowing your database system like the back of your hand is good, but only part of the battle. Coming up with an easy-to-use interface that your users can learn quickly is just as critical.

You could spend a lot of time reinventing the wheel, or you could use Access—a relational database on its own. Unlike SQL Server, Access also offers a variety of development tools and controls for building a flexible and easy-to-use end product. Lots of developers depend on Access to build their front-end applications.

Over the years, Access has proven to be a useful front end for the big databases. Now you have the Access Data Project (ADP), which is much cleaner and easier to work with. An ADP is a specific Access file type that stores user objects such as forms, reports, macros, and Visual Basic for Applications (VBA) code modules. All the other objects—the tables, stored procedures, views, and so on—are stored on the database server. You can use an ADP as a front end to SQL Server in three ways:

  • Convert an MDB file to an ADP file, which will use SQL Server. All the data will be stored on SQL Server, but you'll still use Access' familiar interface to interact with the data. This choice requires a substantial investment in development time because you usually have to manually revamp forms, reports, queries, and so on.
  • Keep your MDB file intact, but link to the server tables from inside the MDB. Doing so will use an ODBC link to the newly upsized tables on SQL Server. The resulting arrangement is slower than the previous one.
  • Upsize data to SQL Server by creating an entirely new database on SQL Server without making changes to the actual MDB file.

Read more

Contact us today for a free consultation!