L
Lungta
This has got me stumped - hope someone can point me in the right direction.
We have a large db split with shared backend on the common drive. Windows
XP/Access 2003, 12 users. Not authorized to make enhancements directly in
Access right now, so can't use Access pivots.
We intend to distribute 8 Excel workbooks with pivots that use Access
queries from the main db as the source. They don't seem to have their hooks
into the db except for the moment of refresh, so we're hoping this means
minimal performance hit.
Question is, if testing goes ok, where in heck do we store the queries on
the real db? Each user will save their own copies of the workbooks for
customizing their pivots. The workbooks can move easily but they
self-destruct if source is moved/renamed. Can't be tied to each person's C:
drive, and can't have everyone accessing 1 shared dummy front end on the
network, or can we?
Seems almost like the source queries should be in the shared back end, but I
would really appreciate input.
We have a large db split with shared backend on the common drive. Windows
XP/Access 2003, 12 users. Not authorized to make enhancements directly in
Access right now, so can't use Access pivots.
We intend to distribute 8 Excel workbooks with pivots that use Access
queries from the main db as the source. They don't seem to have their hooks
into the db except for the moment of refresh, so we're hoping this means
minimal performance hit.
Question is, if testing goes ok, where in heck do we store the queries on
the real db? Each user will save their own copies of the workbooks for
customizing their pivots. The workbooks can move easily but they
self-destruct if source is moved/renamed. Can't be tied to each person's C:
drive, and can't have everyone accessing 1 shared dummy front end on the
network, or can we?
Seems almost like the source queries should be in the shared back end, but I
would really appreciate input.