How to populate a data field with specific date to existing table in access 2010?

[NMACH]

I have a table with more than a million records. I want to add a new column with date euqals to e.g.3/14/2012 for all the records. I am using update query, but it is super slow (taking more than a hour)..is there any other way to do this?



Thanks in advance.

[June7]

Did the update get accomplished? If it did why is time an issue? Do you have to repeat this update periodically? Why? I don't know any faster way to accomplish table update. I doubt VBA procedure using a recordset could do it any faster.

[NMACH]

Thank you for your response.

I have to do this for several different tables. I did accomplish it thru update query for one table. However, for the other table, it didnot update all the records.

In general, does this operation takes longer time? Is it because of the number of records too high this case?

[orange]

Just curious -- Why do you have to add a field to the record/table layout? What exactly is the issue causing/requiring this to be done?
And why for several tables?

It sounds very much like the underlying tables and relationships do NOT match your Business requirements.

[NMACH]

Each file corresponds to a specific date and there are six of these files for 6 six different days. however each file does not have the date field.

In the later stage, i want to combine all these files into a one file and ran queries on that master table. So i want to add the date field before combining into a single master table.

[orange]

I think you should research Normlization.

Normalization links:
http://www.utteraccess.com/wiki/index.php/Normalization (lots of related links here)
http://en.wikipedia.org/wiki/Database_normalization

Good tutorial on tables and relationships -- the procedure will lead you to proper table design.
http://www.rogersaccesslibrary.com/Tutoria...elationship.zip

[June7]

I think you are on right track to get the data into normalized structure. The biggest table I've ever worked with is about 65,000 records and it can run slow for some processes. Can't imagine 6 million records. Maybe Access is not the best resource for your needs. Oracle or SQL might be more suitable