dimpie said:
Thank you so much!!!! It is working faster now.
Much faster?
By assing a field to be indexed, does it change the value in the field
itself. I think it did change some data.
No, indexing does *NOT* change existing data. Indexes are a sorted
list of the data in a field (or fields) kept elsewhere in the MDB.
From Access 97 help.
"Create indexes for fields you sort, join, or set criteria for. You
can make dramatic improvements in the speed of queries by indexing
fields on both sides of joins, or by creating a relationship between
those fields and indexing any field used to set criteria for the
query. Finding records through the Find dialog box is also much faster
when searching an indexed field.
Indexes aren't appropriate in all cases, however. Indexes add to the
size of the .mdb file, reduce concurrency (the ability of more than
one user to modify a page at the same time) in multiuser applications,
and decrease performance when you update data in fields that are
indexed, or when you add or delete records. It's a good idea to
experiment to determine which fields should be indexed. Adding an
index may speed up a query one second, but slow down adding a row of
data by two seconds and cause locking problems. Or it may add
negligible gains depending on which other fields are indexed. For
example, adding an index to a PostalCode field may provide very little
performance gain if a CompanyName field and LastName field in the
table are already indexed. Regardless of the types of queries you
create, you should only index fields that have mostly unique values."
You're quite welcome.
Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog -
http://msmvps.com/blogs/access/