Microsoft Access is a very good database solution, but it has limits. While the portability of mdb and accdb files is convenient, there are advantages to moving to the less portable SQL Server solution. If you do have SQL Server, there's very little reason not to consider migrating your Access Databases. Not all custom-made Access applications easily lend themselves to a SQL Server solution so you'll need to do some analysis before choosing a migration path.
Learn how to deliver dynamic content by building a meaningful Business Intelligence Application, utilizing only what is available on the client's desktop, when a Data Warehouse BI Application, SQL Server and SSIS/SSRS aren't an option.
This article gives a description of the iff() and DLookup() functions in Access 2007, and a method to converting them to SQL.
Access can offer a lot of help with missing values, but finding and generating missing values in a field of sequential values requires a bit of code. Find it here.
Learn how you can use Microsoft Access 2007 as a basic data mining tool for exploring your valuable data. This article illustrates how data filters, pivot graphs, queries in graphs and filters in reports can help this cause.
MS Access can retrieve and measure time with millisecond precision, but only with the help of a few well-known API calls and several user-defined functions.
In a previous tip we saw how easy it was to link to SQL Server tables from Microsoft Access. As is the case with all systems, how does Access manage the changes? What happens when you modify the structure of the underlying SQL Server table? What happens to the SQL Server table if you delete the linked table in Access? We will look at each of these situations in this tip.