Storing reports in a database using a 3-tier design
Hi,
We are using RB in a 3-tier design and will be storing the reports in a
database. Users should be able to create, delete and modify these
reports. Unfortunately the standard way of storing reports to a database
doesn't work since the client application will only see the middle
layer. I wonder what strategies people are using given these
requirements.
I am thinking of saving the report locally to file and when the user
saves the report stream it to the midlle layer. SDon't know if there are
any other feasible solutions.
regards
Paul
We are using RB in a 3-tier design and will be storing the reports in a
database. Users should be able to create, delete and modify these
reports. Unfortunately the standard way of storing reports to a database
doesn't work since the client application will only see the middle
layer. I wonder what strategies people are using given these
requirements.
I am thinking of saving the report locally to file and when the user
saves the report stream it to the midlle layer. SDon't know if there are
any other feasible solutions.
regards
Paul
This discussion has been closed.
Comments
I have always had my own storage mechanism for my client app. (I know DM
does a great job with the integrated DB report storage--it doesn't work for
me for various reasons). I store most of my reports in a DB that is customer
independant and store custom reports in files. I have a number of fields
that describe the reports in each record/ini file. I saw one implementation
when I was visiting a site where a BPL was stored in the DB record that
contained the report--and all the events would be fired inside the BPL. It
was quite slick.
I like keeping tight control over my reports, and in this case you could get
into a management nightmare. Change your middle tier data strucutre and you
could end up having reports that our out-of-sync with the data.
Enjoy.
Ed Dressel
Team DM
My reports will always be stored in a centralized database. The big
question is the mechanism used. Since we are using 3-tier, letting RB
update the database is not a solution. Since end-users must be able to
create/delete/modify reports the middle tier should hev the necessary
functionality to read and write reports.
I am still left with the question how to do this. My idea was to store
the reports locally when the report is saved and use the save event to
stream the report to the middle layer. After this the local rport is
ofcourse thrown away and only the reports stored in the database are
ever used.
I haven't heard any other solutions yet...
regards
Paul
In article <3e41b5b8$1@dm500.>, "Ed Dressel [Team DM]"
at "Ed Dressel [Team DM]"
says...
With your needs, you will have to come up with your own implementation. This
is not difficult to do. If you want an example, send me an e-mail and I will
give you a link to my current product and show you how I designed my own.
(And edit my email address as noted in it--and please keep any specific
questions in the newsgroup).
Enjoy.
Ed Dressel
Team DM