Thanks. I have never declared a recordset and was not sure if it would speed
things up.
We run a report every morning that pulls a lot of patient info for people
that are currently in the hospital. This report runs thru about 5500 names to
spit out 25. Would there be any benefit to using a record set here?
Perhaps you could give me some examples of when you declare them.
Hi Patti,
Recordsets aren't for speeding up existing functionality. They're for
doing something that is difficult or impossible to do with queries
alone.
For your performance issues, I suggest that you look at the queries
that your report is based on. When you say "run through about 5500
names", what do you mean? Does the report use selection criteria to
select just the 25 records? How fast does the query run by itself?
Have you tried adding indexes to the tables on fields that are used
for sorting and selecting the records?
In other words, recordsets aren't your answer here. But there might
be other things you can do to speed up your report. Maybe we can help
if you post more details.
Armen Stein
Microsoft Access MVP
www.JStreetTech.com