Prev: Config Transforms with Web Deployment Projects in ASP.net
Next: ASMX in Framework 4.0
From: Cubaman on 16 Jul 2010 05:15
On Jul 16, 2:14 am, "Alan T" <alan_NO_SPAM_pl...(a)yahoo.com.au> wrote:
> Hi,
>
> Unlucky, as we are using MySQL as backend.
>
> Also a question in my situation:
> - we got 80 reports
> - each report have different parameters (filters, may be 4 or 5 filters)
> - for my second option (write a Windows service scanning through the table)
> - if I store each type of report request in its own table, there will be 80
> tables with one master table(the queue) which points to each possible report
> table (one of those 80 tables)
> - if I use 1 big table as request queue, there will be about 30 fields
> storing the parameters (many of the parameter fields will be empty, first
> normalisation, but I don't mind this)
>
> "Cubaman" <oscar.acostamonte...(a)googlemail.com> wrote in message
>
> news:12f888e5-3dd0-44a9-a3c7-8f37c40e3528(a)s9g2000yqd.googlegroups.com...
> On Jul 13, 2:36 am, "Alan T" <alan_NO_SPAM_pl...(a)yahoo.com.au> wrote:
>
> > Just wanted to know if I can do this:
>
> > 1) User click a button on a page
> > 2) It creates a thread
> > 3) The thread will generate a report
> > 4) This process may take up to a couple of minutes. eg. 5 minutes
> > 5) Before the process finish the client exit and close the browser
> > 6) The process will still keep doing its job until the report/file is
> > generated
>
> > Do you think it is possible?
>
> > The reason I am think of this way is the user does not need to wait for
> > the
> > 5 minutes keep the browser opening in blank mode.
>
> I think that you should try Sql Reporting Services. It comes with Sql
> 2005 for free, and can generate reports in push or pull mode.http://technet.microsoft.com/en-us/library/cc917530.aspx
> Best regards.

Dont store reports in ddbb, but in file system. Just save the path an
other relative data in ddbb. Is the most common aproach.
Best regards.
From: Alan T on 18 Jul 2010 19:14
> Also a question in my situation:
> - we got 80 reports
> - each report have different parameters (filters, may be 4 or 5 filters)
> - for my second option (write a Windows service scanning through the
> table)
> - if I store each type of report request in its own table, there will be
> 80
> tables with one master table(the queue) which points to each possible
> report
> table (one of those 80 tables)
> - if I use 1 big table as request queue, there will be about 30 fields
> storing the parameters (many of the parameter fields will be empty, first
> normalisation, but I don't mind this)

Dont store reports in ddbb, but in file system. Just save the path an
other relative data in ddbb. Is the most common aproach.
Best regards.


Hi,

Yes, I saved the exported reports in file system in .pdf format.
What I will save the report requests in table.

eg.
Master table:
ID
RequestUser
RequestDate
RequestReport ID
HasSaved
HasStarted

Detail report request table:
ReportID
ReportName
EmployeeID
Start Date
End Date
.......
.......
Filter30

So as each report will have about 4 filters (eg. DateFrom, DateTo,
EmployeeID, ...etc)
Most of the Filters fields will be empty.

My service will scan through the master table to see if any of the requests
had started and saved., set a flag if yes.
Then look for the details table for the filters and generated the report.

eg.
Generate Employee report, will take the EmployeeID, Start Date and End Date
for the report filters.



First  |  Prev  | 
Pages: 1 2
Prev: Config Transforms with Web Deployment Projects in ASP.net
Next: ASMX in Framework 4.0