obe

Hello
I have several programs that do a lot of calculations and
creates/updates records on SQL Server 2000. When the program is started
the user has to wait until it is completed before he/she can do
anything else with the computer. The user can se the progress of the
job in the window. I would like to know what would be the best solution
to have this program run in the background. The background job should
then notify the user when it is complete. I don't want the computer
to be "locked" during the process. Is it possible to have the job run
as a job on SQL Server, and when it's completed send e message to the
user that started it?
I am looking for something like how background jobs "batch jobs" works
on the as400.

Any Suggestions?

Thanks,

obe

Hello
I have several programs that do a lot of calculations and
creates/updates records on SQL Server 2000. When the program is started
the user has to wait until it is completed before he/she can do
anything else with the computer. The user can se the progress of the
job in the window. I would like to know what would be the best solution
to have this program run in the background. The background job should
then notify the user when it is complete. I don't want the computer
to be "locked" during the process. Is it possible to have the job run
as a job on SQL Server, and when it's completed send e message to the
user that started it?
I am looking for something like how background jobs "batch jobs" works
on the as400.

Any Suggestions?

Thanks,

tim robinson

What is the program doing that's stopping the user from switching to another
app? It shouldn't be possible to disable multitasking, which is what I think you're saying.


If you want to run the program without having it display a UI, you should
explore the options that CreateProcess gives you.


What is the job in question? Is it actually a Windows app? Or is it a stored
procedure, which is locking the database? The answer depends on what you're
dealing with. (How to stop stored procedures locking the database is outside
the scope of this newsgroup.)

--
Tim Robinson
MVP, Windows SDK