G
Guest
I have a number of installations of an mde file I have distributed (Access
2000). It has a separate backend tables file.
Several users have asked if they can develop and include their own reports
in the mde database. As I don't want to provide the mdb file for them to
play with I thought of allowing them to create their own reports in their own
second access file linked to the tables. When they were happy with the
report, they could import them into my mde. I could then use a table to
identify the custom reports. By using a combo box and a button to run the
selected report, I can fulfill their requirements. The problem is that you
do not have the option to import a report into an mdb through the Access
import menu.
My options seem to be:
1. Tell them all custom reports must be run from a separate mdb file that is
linked to the data. They have to open the separate file and run the report
which is not ideal.
2. Somehow, using vba, inport the reports from the second file once they
have been developed.
3. Open the reports in the their database somehow from my mde database.
I am sure this is not the first time someone has had to face this option. I
would appreciate any comments on 2 or 3 (or any other options) so that I can
get away from only having option 1.
2000). It has a separate backend tables file.
Several users have asked if they can develop and include their own reports
in the mde database. As I don't want to provide the mdb file for them to
play with I thought of allowing them to create their own reports in their own
second access file linked to the tables. When they were happy with the
report, they could import them into my mde. I could then use a table to
identify the custom reports. By using a combo box and a button to run the
selected report, I can fulfill their requirements. The problem is that you
do not have the option to import a report into an mdb through the Access
import menu.
My options seem to be:
1. Tell them all custom reports must be run from a separate mdb file that is
linked to the data. They have to open the separate file and run the report
which is not ideal.
2. Somehow, using vba, inport the reports from the second file once they
have been developed.
3. Open the reports in the their database somehow from my mde database.
I am sure this is not the first time someone has had to face this option. I
would appreciate any comments on 2 or 3 (or any other options) so that I can
get away from only having option 1.