Access 2007-2016
Access 2000-2003
Access Seminars
TechHelp Support
Tips & Tricks
Access Forum
Course Index
Topic Glossary
Insider Circle
Home   News   Tips   Glossary   Templates   Forums   Help   Logon   Order   Contact Us  


Microsoft Access Forum
By Richard Rost   Richard Rost on Facebook Richard Rost on Twitter Richard Rost on Google Plus Richard Rost on LinkedIn Email Richard Rost

This forum is for the discussion of Microsoft Access.

Access is my personal specialty. Have questions? Comments? Want to discuss how to do something? Post it here. Also, I get a LOT of questions sent to me in Email from people around the world. I'll post the interesting ones in here. Feel free to comment on them.

Click Here To Subscribe to this forum and receive an email update whenever new posts are added, just scroll down to the bottom of this page and enter your email address in the comment form.

Permanent Link
Keywords: microsoft access forum
Post New Topic

Read Indexing by Marianne @ 12/7/2017
Still learning. I can't seem to wrap my head around this indexing thing.

I have an Interaction table where I want to keep notes for every interaction with a customer.

My Customer table includes a SSN field.

I want to be able to add multiple Interaction entries under one Customer ID, but that would create multiple SSN's.

When I try to enter in a new interaction, I'm met with an error that says I can't because it'll create duplicates and that's not allowed.

Ugh. Maybe that didn't make any sense.

I think I'm getting confused with the SSN's and the Customer ID. I want multiple entries for SSN's, under one Customer ID. But I don't want the SSN's duplicated anywhere else.

Reply from Alex Hedley:

Interaction should only contain CustomerId and any fields associated with the Interaction, nothing more to do with a Customer.
If you need the SSN in a report etc create a Query that Joins CustomerT with InteractionT based on the CustomerID
Show Just This Thread        Post Reply
Read Indexing by Michael G @ 1/4/2015
Thank you, this was helpful.  It was strange: I only had 4 fields indexed, but I had a lot of tables (for combo boxes and subforms) joined to the main table, and it seemed to want to limit the number of tables because it popped up that there were too many "indexes".  So I created a new table, joined it to the original main table, and then its primary key seemed to accept more combo box and subform tables off of it.  I just had to figure out the Record Source for the second form because it had duplicates from the initial primary table plus the content from the new one.  But the query join seemed to work, so that was exiting. It all seems to be in working order.  My queries across all the tables that are joined are all coming out favorably.  Now we're going to dump a lot of data into the Database, and we'll really find out if everything is kosher.  Thanks again.
Show Just This Thread        Post Reply
Read Indexing by Michael Goins @ 1/3/2015
I tried to index several of the fields in a table, and I am getting pop-ups that say I have too many indexed fields.  It was my understanding that we could index as many fields as desired?  Please advise.  Thanks.

Reply from Alex Hedley:

The maximum Number of indexes in a table is 32.
If you try saving one at a time does that help?
It does add overhead so I wouldn't do too many, ones that you are likely to search on like Dates.
Show Just This Thread        Post Reply
Read Indexing by Pam @ 9/27/2013
My point is  I could have xxxxxx111111 for 2.09 and the same number xxxxxx111111 for 3.09. So you ca not index on this field because the number may have more than one charge.  Indexing with no duplicates will keep additional charges for this number will keep additional costs from entering the database. Thanks

Reply from Richard Rost:

You're right... then you can't index that value no duplicates, nor should you want to. If this field is analogous to an ORDER NUMBER, then you should have the individual charges in a SEPARATE details table.
Show Just This Thread        Post Reply
Read Indexing by Pamela @ 9/24/2013
Hi Richard, I am trying to make sure that I am creating my tables correctly. I have employee ID Number  and a  alternate field. The alternate field consist of their ID number and a travel number. (EX. IDNUMBERTRAVELNO or 111111T4444444444.) I can not index on the ID number alone because some people do not have ID numbers in the database and I could miss some travel transactions from employees without an ID number. Is there another alternative?
Indexing - no duplicate records failure. I have 3 databases with duplicate ID numbers and the travel numbers listed. I want to append to the database weekly but I can not because of the duplicate ID Fields and travel numbers. This is causing me heartaches, are there other alternatives? Thanks

Reply from Richard Rost:

As long as you have the field set to INDEXED: YES (NO DUPLICATES) and the REQUIRED value to NO, then you should be able to still catch duplicates even though some people might not have ID numbers.
Show Just This Thread        Post Reply

Collapse All Topics


Post Your Comments or Subscribe
    If you would like to be notified of new posts on this forum,
    just enter your email address below. It will be kept private.
If you just want to subscribe to get email updates when this forum is updated, then enter your name and email address and check the Notify Me box below. If you would optionally like to add your comments below to be posted, they are welcome.
  Your Name:  Required
  Your Email:  NOT Public


Sorry about this step. It's just to keep the spam bots away:
  Verify: What is 7+2:
  Notify me when the this forum is updated
  Remember Me for my next comments
Please do not use this form for Customer Service inquiries! If you have questions about your account, shipping info, courses you've ordered, need passwords, etc. please use the Customer Service Center instead.

I value your comments. They will be displayed on this page (above). Your name will be displayed, but your email address will not be.
As always, I promise to never give away your personal information to anyone else, ever.

NOTE: If you don't leave your name and email address, DON'T expect a reply. I can't promise a personal reply to everyone who posts here. I TRY my best, but I cannot guarantee it. If you don't leave your real name and email address, I won't even bother. I usually just hit DELETE. -Richard



You may want to read these articles from the 599CD News:

8/25/2018NEW: Access Dev 9, 10, 11
8/25/2018Microsoft Access Developer 11
8/25/2018Microsoft Access Developer 10
8/25/2018Microsoft Access Developer 9
8/23/2018Access Dev 11 is ONLINE
8/17/2018Access Dev 10 is ONLINE
8/15/2018Access Tip: Search Form
8/15/2018Access Tip: Locked v. Enabled
8/15/2018Access Dev 9 is ONLINE
7/31/2018Microsoft Access Developer 8

Visual Basicindex
Account Login
Online Theater
Lost Password
Free Upgrades
Insider Circle
Student Databases
Change Email
Latest News
New Releases
User Forums
Topic Glossary
Tips & Tricks
Search Our Site
Waiting List
Production Schedule
Collapse Menus
Live Chat
Customer Support
WalkThru Tutorials
Consulting Services
About Us
Affiliate Program
Richard Rost
Free Lessons
Mailing List
Video Tutorials
MYOLP Memberships
Idiot's Guide to Excel
Volume Discounts
Payment Info
Terms of Sale
Gift CDs
Live Chat
General Info
Support Policy
Contact Form
Email Us
Mailing Address
Phone Number
Fax Number
Course Survey
Facebook    Twitter

Google Plus    LinkedIn

Blog RSS Feed    YouTube Channel
Richard Rost Microsoft MVP