C# -- Reporting ''Job'' Numbering

Please review the below and let me know (1) what C# tools you would use and (2) what parts of the below 6 items you would need to change so it works with your tools. I will then post a few sample datatables and provide additional data so you can create the sample APP. Possible Tools a. Microsoft SQL Reporting Services 2005 b. Oracle Discoverer c. Microsoft SharePoint Portal d. Oracle Portal e. C# EventHandlers f. Microsoft Message Queuing g. Windows Workflow Foundation ** this might be the best ? h. C# events i. others ? Basically, I am using C# 2008 and want to create an APP similar to the below mainframe steps. =========================================== 1. user logins to application and runs a OrderProcessing or Reporting job ** OrderProcessing / Reporting logic is stored in a database Package 2. data (job #, time, username, and jobname) gets written to database and "Job #123, Started 9:45am, Order Processing" appears on user’s "Alert" screen 3. log (which shows what code is running, SQL statements, etc) gets created in //server/jobs/[login to view URL] for troubleshooting if report fails 4. message appears in lower left of user’s computer when job is done, like Microsoft Outlook’s "New Message Icon" and a the timedone column gets updated in the database 5. job displays "report exceeded 50,000 records" message on last page to eliminate users from printing a report that is TOO many pages long ** this does not eliminate the system from doing its preprocessing, therefore it might be easier to do some "if job has been running for over 60 minutes and job type = R, then suspend and send an email to sysadmin" ** please let me know what other IDEAS you have 6. job then ** autoprints if user selected a printer OR ** goes to user’s MyDocs/temp folder as PDF or Excel (depending on what option they selected) ## Deliverables 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables): a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). ## Platform Microsoft C# 2008