New report in a MDE Database

  • Thread starter Thread starter John Henriksen
  • Start date Start date
J

John Henriksen

Hi group

I got a access 2000 mde database that are distributed to a number of users.

Now I want to give them a new report.

How can I acomplish that, whitout making a new mde database.

For your infomation I am an expert in making Access databases for 10 years
now
So feel free to give me all you have including API and so forth.

Thank you for your help

John Henriksen

Denmark
 
Well thats true and yes the database is split to front end / back end
but the database is about 6-7 mb and the user should only download the
relevant report (more than 200 reports are avaible)
therefore only the relevant repports should be downloaded to the system

Thanks for the answer

John
 
Well thanks for the answer

And Yes of course the database is splitted to a front/back -end
I was trying to simplify the case. I can't give all the tecnical details it
would be a long story
I was just hoping that there was a solution to make some kind of reports
outside the mde database, that was not compiled
or a non documented feature to implement a new report into the mde database.

Thanks for your time

Maybe some report generator whould be the solution.

Thanks for you answers, I can see you are an expert in database solutions

John
 
Well that was my first solution, to zip the file, but there is another issue

When you make changes to you database mdb and the make a new mde you
database will grow easely to the double size everytime you make a new
report, of course that you can fix that. but you know that ower time your
database will be corrupted and then you have to make a new fresh database
compiling it making a new mde , make a zipfile and so forth. lots of work
to do

Maybe the solution would be to let the users have the mdb file... but then
again the solution will be slight slower couse of the recompiling everytime
the user starts the database. an mde database is more realaible.

I'll have to find the ultimate solution for the case

Thanks for your answers

John
 
Well that was my first solution, to zip the file, but there is another issue

When you make changes to you database mdb and the make a new mde you
database will grow easely to the double size everytime you make a new
report
Click to expand...

The mdb will grow, but since you are disturbing a mde, then that should not
be a problem. The size increase of the mde when adding a report and the
resulting growth is usually very small.

The other approach I find is that often one report can do double, or even
triple duty. For example, I used to create a lot of reports with details,
and then a copy of the same report with NO details. I now use the same
report, but just "toggle" the details visible in the forms on-open event.
Thus, the same report can both show details, or no details. In addition, if
you look at the following report form examples, you will see that I can add
new reports to the system, and not have to modify the UI as most reports are
selected from a listbox. Generally, after a few months, I find the clients
stop requesting new reports since they already have what they need by given
them options like date ranges etc..

Here is some screen shots of what I mean:

http://www.attcanada.net/~kallal.msn/ridesrpt/ridesrpt.html
 
Very nice solution you have make and I think that it fit to your solution,
with similar datastructure thats is a great solution

The systems I use to develop is always modular, so that I allways can take
one modul out whitout inflecting the other.
Typical the user do have some very special reports for there use eg. logo
and so.

I think I will develop the reports i another report generator and then pass
the data to the report that way.
My goal is that a report can leve with in its own module. I wont bind
modules to tight (bad database/program design)

John

Take care
 
It sounds like you have reporting requirements down to the
user & maybe the knowledgable(?) user might want to query
some data and produce their own custom reports. These
people exist in every organization. I distribute a second
piece of my access front end for custom reporting. This
piece brings down the data that that user has access to.
This can be updated by the user by the click of a button.
This gives the user the ability to run his own reports,
reduces hits on the DB and prevents any user from
accidently corrupting data.

Good luck

Jim
 
Back
Top