Can we create multicolumn unique indexes on MS access databases?

by

Turns out you can create a multi-column unique index on an MS access database, but it’s a little crazy if you want to do this via the GUI. There’s also a limitation; you can only use 10 columns per index.

Anyway, here’s how you create a multi-column unique index on an MS access database.

  1. Open the table in design mode, and Design, select Indexes.
  2. Create a new row and enter a value in the Index Name cell,
  3. Choose the first column from the drop down menu.
  4. Add a new row and leave the Index Name cell blank.
  5. Choose the second column, and so on.

Here’s what it should look like:

multicolumn index in MS access

More Related Contents:

  1. How to design a product table for many kinds of product where each product has many parameters
  2. What is Normalisation (or Normalization)? [closed]
  3. Database design – articles, blog posts, photos, stories
  4. Schema for a multilanguage database
  5. Calendar Recurring/Repeating Events – Best Storage Method
  6. How to version control a record in a database [closed]
  7. designing database to hold different metadata information
  8. Same data from different entities in Database – Best Practice – Phone numbers example
  9. Sql – Indirect Foreign Key
  10. What are the lengths of Location Coordinates, latitude and longitude? [closed]
  11. Are nulls in a relational database okay? [closed]
  12. How should I implement this schema in MongoDB?
  13. Why use multiple columns as primary keys (composite primary key)
  14. Database schema which can support specialized properties
  15. How do you deal with polymorphism in a database?
  16. Nullable Foreign Key bad practice?
  17. How do I design a database to store properties, selecting attributes by synonyms
  18. Composite primary key or not?
  19. Hash Collision – what are the chances? [closed]
  20. How do you determine how far to normalize a database?
  21. Should I have a dedicated primary key field?
  22. Setting up an MS-Access DB for multi-user access
  23. What is the best database schema to support values that are only appropriate to specific rows?
  24. Database design for audit logging [closed]
  25. Should I use a single or multiple database setup for a multi-client application? [closed]
  26. Database Design Best Practices [closed]
  27. SQL: Using NULL values vs. default values
  28. Bill of materials database model
  29. What are design patterns to support custom fields in an application?
  30. mongodb schema design for blogs

Leave a Comment