G
Gordon
I got a question that concerns the technologies available
in MS Access:
I've got an Access DB that processes financial data each
month. Then, each month a report will go out to each
department (there are 100 departments) which will show
them expenses for their department only. I want to set
something up so that each department can access their own
data for Viewing Only, but can't access any other
department's data. The departments will be viewing this
report pretty much at the same time.
In the past, I've been able to set up a second 'Reporting'
Access DB which just contains the report, and this is
linked to the table in the first DB, but this didn't work
as well with multiple users viewing at the same time, and
I don't want to have to provide a copy of this 'Reporting'
DB to each of the 100 departments.
What is the best route to take to design something like
this? Data Access Pages? XML? Snapshot format?
Thanks,
Gordon
in MS Access:
I've got an Access DB that processes financial data each
month. Then, each month a report will go out to each
department (there are 100 departments) which will show
them expenses for their department only. I want to set
something up so that each department can access their own
data for Viewing Only, but can't access any other
department's data. The departments will be viewing this
report pretty much at the same time.
In the past, I've been able to set up a second 'Reporting'
Access DB which just contains the report, and this is
linked to the table in the first DB, but this didn't work
as well with multiple users viewing at the same time, and
I don't want to have to provide a copy of this 'Reporting'
DB to each of the 100 departments.
What is the best route to take to design something like
this? Data Access Pages? XML? Snapshot format?
Thanks,
Gordon