D
DawnTreader
Hello
a while ago i posed some questions regarding my current frontend set up. i
now have a little question about the backend. i have a database where all the
current live data is stored. my 3 frontends are connected to this and each
frontend is used by a specific kind of user. at some point i will be melding
the three frontends into one, but in addition to the frontend situation i now
have a "report" end question.
there are a bunch of queries that i had made that i couldnt put in a
frontend because they are used by excel workbooks to pull data for a bunch of
pivot tables. so i put these queries in a front end because i didnt want to
bloat my backend db.
the problem is that i need to now have some functions that i made in this
"report" end in order for some new reporting that i need to do. additionally
i dont like having all these queries hanging out in this seperate database.
some of the queries there are duplicates of ones in my frontend(s).
i am wondering what the best solution to this is...
do i :
collapse the report end back into the backend current live db?
do i put the report queries in the frontend(s) and leave a copy somewhere
the excel files will always be able to find it?
instead of putting the pivot tables and charts in excel should i build them
into a form in my app?
i need to create a "dashboard" type report feature sometime in the future,
what can i do now with these reports that would make it easy and efficient to
create this?
is there a web software creation tool that i can use to create a report
"dashboard"?
as always, thanks for any and all suggestions.
a while ago i posed some questions regarding my current frontend set up. i
now have a little question about the backend. i have a database where all the
current live data is stored. my 3 frontends are connected to this and each
frontend is used by a specific kind of user. at some point i will be melding
the three frontends into one, but in addition to the frontend situation i now
have a "report" end question.
there are a bunch of queries that i had made that i couldnt put in a
frontend because they are used by excel workbooks to pull data for a bunch of
pivot tables. so i put these queries in a front end because i didnt want to
bloat my backend db.
the problem is that i need to now have some functions that i made in this
"report" end in order for some new reporting that i need to do. additionally
i dont like having all these queries hanging out in this seperate database.
some of the queries there are duplicates of ones in my frontend(s).
i am wondering what the best solution to this is...
do i :
collapse the report end back into the backend current live db?
do i put the report queries in the frontend(s) and leave a copy somewhere
the excel files will always be able to find it?
instead of putting the pivot tables and charts in excel should i build them
into a form in my app?
i need to create a "dashboard" type report feature sometime in the future,
what can i do now with these reports that would make it easy and efficient to
create this?
is there a web software creation tool that i can use to create a report
"dashboard"?
as always, thanks for any and all suggestions.
have an awesome day