>I was given a requirement to build a system for reporting. I have an idea of what I want to do but I just need to confirm everything with everyone, please.
>
>Requirements:
>Have an interface that an enduser can request reports and have it act like a regular report option from the application. This can be an exe/app being called from an application.
>
>This interface must be able to print reports on-demand, schedule reports and process reports simultanously. For example: Pancho request a report that may process for 2 hours while Maria request a report that can be processed within 2 minutes. The system must be able to continue processing Pancho's report while Maria's report isn't held up for 2 hours.
>
>Possible Solution:
>At first thought, MSMQ came in to mind. But, I'm not sure MSMQ can start an application thread since it's only messaging. Second thought was not involve MSMQ and just have a centralize database that can hold the reporting information while having three applications work together to complete the task. One application would be the User Interface while the second application watches the centralized database for new request and lauches new instance of VFP for the third applcation thread to run the necessary reports. This will keep the UI and the "Watching" application free of any process while a third application can be fired into it's own thread to perform all the intense process.
>
>It seems like alot to me and I'm trying to simplify it but based on the requirements this may be the only way to do it.
>
>Your feed back is appreciated.
Why not use a COM to do the reporting for you? That com could task through MSMQ for various tasks, giving you the best of both worlds?
__Stephen
