Append different values to same column

vadharah

Registered User.
Local time
Today, 13:40
Joined
Oct 14, 2008
Messages
35
Is it possible to append different values to the same column at one go?

I have a field that can take 3 different values from a look-up table so there really wont be any duplications is it possible to write all this in a single append query?

I am getting an error saying 'duplicate output destination'
 
An Append query can add many records to a table. An Update query can modify fields in many rows. Do you want to add new records or do you want to update existing records?

Use the WHERE clause to select the records to amend. You need to give more information if you want more detailed help.
 
An Append query can add many records to a table. An Update query can modify fields in many rows. Do you want to add new records or do you want to update existing records?

Use the WHERE clause to select the records to amend. You need to give more information if you want more detailed help.

Rabbie

I have a table with a field (Cars) the type of cars are stored in a look-up table and contains 5 names of cars. Then i have a form with all the names of the cars and from a dropdown list the user selects the usage of each car (never, daily, weekly, etc). The table i need to update has 3 columns i.e CompanyID, TypeOfCar and frequency all three fields forming the primary key.

ideally my table would look like this:


12 Mazda Weekly
12 Benz Daily
12 Vauxhaul Weekly
17 Mazda Never
17 Benz Never
17 Vauxhaul Daily


12&17being the CompanyID

How do i write this in a single append query?
 
To produce an Append query you need to basic on an ordinary Select Query which you can then change into an Append query. You have told us what you want the result to be but from your description it seems that a lot of your data is selected by the user from Combo boxes or similar.

Is your form collecting all the data before the query would be run.

It might be better to have a bound form that populates each record as they are filled in and then you wouldn't need the query at all.

Compound primary keys are often not very efficient and so it might be better to have an autonumber primary key. This will make the indexing more efficient.
 

Users who are viewing this thread

Back
Top Bottom