Recent content by one3nine0

@Mark @Pat Thank you both so much. Your information helped me figure this out!

Ok, I think I may have figured out why my relationships aren't working. I did not realize that my customer ID had to be a long integer data type in order to establish a one to many relationship. My customer ID field from Excel is "Double". I'm going to change my customer info table so that I...

So yes, the customer number will always be unique and not change. To make the customer number the key I would follow the example here? stackoverflow.com/questions/24238068/access-sql-alter-column-to-autonumber

So I get an excel download from SAP of the customer info every day, that automatically replaces the old file. This process is something someone else set up and I am using. The customer numbers are part of this download. I linked that file into Access, but realized I needed to make some changes...

I am using an unbound combo box to filter for the main form records. I think an issue is that the customer number is not an autonumber, it is a number a different division set up, and I was hoping that by indexing it (with no duplicates) that it would be treated the same and let establish a...

I have two tables: Customer Info and Notes Customer Info: Customer number (Unique Index), Customer Name, Etc Notes: NoteID (Key), Note Date, Notes I established a one to many relationship, and then created a form based off of the Customer info table, and use it to auto populate fields from the...