Transposing Data in Microsoft Access Tables and Data Normalization

Microsoft AccessMicrosoft SQL ServerData normalization is fundamental to database design. Properly normalized data makes it easy to support an application over time and simplifies the querying, displaying, and reporting features of an application. 

Unfortunately, we don’t always receive or have normalized data. Tables that require adding fields as the data changes over time are particularly problematic and violate the basic premise of database design where adding records is free, but adding fields is expensive:

Here are some updated resources detailing the value of data normalization, including a sample database and VBA code to transpose and normalize your existing data.

These and other related papers are part of our developer centers:

Hope these help you create more scalable, maintainable, and analyzable databases.

For advanced data analysis, check out our Total Access Statistics add-in product.

2 thoughts on “Transposing Data in Microsoft Access Tables and Data Normalization

  1. I have a quick question. I have a sysprep file for Win7 32-bit that was created by the tech before me at my company. The file works perfectly. We are now looking at going to Win7 64-bit on some machines. I’ve tried creating a sysprep file for Win 7 64-bit, but I keep getting errors. I was wondering if I could copy the existing 32-bit file and replace the x86_XXX… entries with amd64_XXX. Would that work or am I not going to be able to do that?