By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
448,560 Members | 1,449 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 448,560 IT Pros & Developers. It's quick & easy.

Query: Adding record when source table is Null

P: 1
(Sorry this is so long, was trying to fully explain the situation) There are two tables that handle information on our clients. Every client has a unique ClientID, and the ClientID is the Primary Key for the records.

I have a query that displays fields from both tables, but while one of the tables, the main one that hold the Contact information has ALL of the clients in it; the other table holds additional, optional information, so does not have a record for every client.

The Join Properties is set for the ClientID/Primary Key to show all of the records from the Contact table, and only the information from the Optional table “where the joined fields are equal”. So if a client does not have a mention in the Optional table, then the cell for a field from the Optional table is blank, but the cell for a field from the Contacts table holds information, since all clients have a mention in the Contacts table.

Ok, here is the problem: I can not type information into one of those blank cells. I though, since the tables are linked by the ClientID/Primary Key, that a new record would be created in the Optional table (the new record having the same ClientID/Primary Key that the rest of the row/record is working off of) and the information typed into the blank cell be stored there automatically.

Instead it is locking the cell, because there is no record in the optional table for that ClientID/Primary Key, so there is no place to store the cells information.

How can I link the tables ClientID/Primary Key together in regards to a Null record? :confused:
Jul 12 '06 #1
Share this Question
Share on Google+
1 Reply

P: 28
Your last line is explaines exactly why you cannot do what you are attempting. After you run the query and it displays, access has no way to create a record for the blank boxes as it cannot know which primary record the data refers to.

I cannot think of any logical reason why you are splitting up client data into two tables. Wouldn't it just be easier to combine the two tables and then create forms/queries to display the data you need?
Jul 13 '06 #2

Post your reply

Sign in to post your reply or Sign up for a free account.