J
JulieFlynt
This question is from a student of mine. They have a database that is being
shared with a FrontPage frontend for access across an intranet site.
I began using the Yes/No field in our main table to identify particular
billing sites.
So I setup...
- Table with a new Yes/No field (pre-existing table)
- New Query to return results
- Report (created from the query)
However, whenever I run the report, it seems to make the database
unavailable (momentarily) for other users.
The goal is to create a report that can be run by an accounting person
anytime against our DB, but I don't want the queries to impact the other
users.
Any immediate thoughts.
shared with a FrontPage frontend for access across an intranet site.
I began using the Yes/No field in our main table to identify particular
billing sites.
So I setup...
- Table with a new Yes/No field (pre-existing table)
- New Query to return results
- Report (created from the query)
However, whenever I run the report, it seems to make the database
unavailable (momentarily) for other users.
The goal is to create a report that can be run by an accounting person
anytime against our DB, but I don't want the queries to impact the other
users.
Any immediate thoughts.