User authored reports?

[Gary Wright]

I have a fairly large application in which the users seem to frequently want
their reports changed - even if it is just the layout. What is the best way
to allow users to create their own reports, or at least modify ones that I
create for them? I have a split db and the reports are all included in the
compiled front end MDE file so they can't get at them even if they run
Access. I don't think that I can move the reports to the back end and link
to them like tables but maybe I can make another front-end that just
contains reports, leave it as an MDB file and in my regular front end, open
the that database and call the reports there. It seems a bit awkward and
backwards though. Any other suggestions? I don't want to leave the
front-end as and MDB to avoid giving out the source code.

Am using Access 2k, with most clients running full access but others the
run-time version.

Thanks,
Gary.

[Rick Brandt]

"Gary Wright" <gw*****@pd.jaring.my> wrote in message
news:bo**********@news6.jaring.my...

I have a fairly large application in which the users seem to frequently want their reports changed - even if it is just the layout. What is the best way to allow users to create their own reports, or at least modify ones that I create for them? I have a split db and the reports are all included in the compiled front end MDE file so they can't get at them even if they run
Access. I don't think that I can move the reports to the back end and link to them like tables but maybe I can make another front-end that just
contains reports, leave it as an MDB file and in my regular front end, open the that database and call the reports there. It seems a bit awkward and
backwards though. Any other suggestions? I don't want to leave the
front-end as and MDB to avoid giving out the source code.

Am using Access 2k, with most clients running full access but others the
run-time version.

I would give them a separate MDB with nothing but the table links in it and
let them build their own reports in that. You could include some existing
reports to use as templates.
--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

[paii, Ron]

With a 2nd front-end you will need to setup Access security if you haven't
already, otherwise your users will be able to edit the tables on your
backend.

"Rick Brandt" <ri*********@hotmail.com> wrote in message
news:bo*************@ID-98015.news.uni-berlin.de...

"Gary Wright" <gw*****@pd.jaring.my> wrote in message
news:bo**********@news6.jaring.my...

I have a fairly large application in which the users seem to frequently want

their reports changed - even if it is just the layout. What is the best

way

to allow users to create their own reports, or at least modify ones that

I

create for them? I have a split db and the reports are all included in

the

compiled front end MDE file so they can't get at them even if they run
Access. I don't think that I can move the reports to the back end and

link

to them like tables but maybe I can make another front-end that just
contains reports, leave it as an MDB file and in my regular front end,

open

the that database and call the reports there. It seems a bit awkward and backwards though. Any other suggestions? I don't want to leave the
front-end as and MDB to avoid giving out the source code.

Am using Access 2k, with most clients running full access but others the
run-time version.

I would give them a separate MDB with nothing but the table links in it

and let them build their own reports in that. You could include some existing
reports to use as templates.
--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

[Gary Wright]

An interesting way to approach that. Thanks!

I would give them a separate MDB with nothing but the table links in it and let them build their own reports in that. You could include some existing
reports to use as templates.
--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com