Report Generator dilemma.

[GeeWond3r]

I've set up a web application which calls the stored procedure to generate a report to this tmp_table. Now initially, it was meant for 1 or 2 users for this apps, so there'd be no (or should i say not much conflict). But now, the #s of users who uses this application (esp. at the same time) is inflicting this dilemma where data are mismatched. Each user has different reports, and there're cases where one user has the other users' data. Ouch!

I was wondering if anyone has a solution to this dilemma.

Oh... I'll thank you ahead of time for anyone here who can help solve this!!

 

[vongrunt]

1. Create separated temp table for each report.
2. Use the same tmp_table but introduce UserID, ReportID or something.
3. Export report data out of database (serialized recordset, XML stuff, whatever) into a file w/ unique filename.

All methods mentioned have pros and cons - depending on existing app.
In most cases (1 & 3 surely) you'll need extra table containing info who requested report, where is data located etc.

 

[SQLSister]

Are you using real temp tables (name starts with #or ##) and are they local or global?

Questions about posting. See faq183-874