In article <2jp6uvsuct8d04iqh8lejako088cd4sg8v@4ax.com>, Mary Chipman
<mchip@nomail.please> writes
[quoted text, click to view]

If you want something more customised then you can write it, and using
SQL-NS will help. An example job manager can be found here-

http://www.sqldev.net/sqlagent/SQLJobMan.htm

Note that SQL-NS is not a redistributable component so you will still
need Enterprise Manager installed. I wrote my own job manager program,
because I wanted a consolidated view of all jobs across all my SQL
Servers, not just one at a time. Have a look at SQLJobMan and also the
SQL-NS samples that come with SQL Server.

--
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com

PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org

hi Spencer,
"Spencer" <spencer@tabbert.net> ha scritto nel messaggio
news:57dd3c13.0312191013.7b44c28d@posting.google.com...
[quoted text, click to view]

in addition to Mary and Darren post, you can have a look at a free prj of
mine, written in VB6 using SQL-DMO (which is redistributable) at the link
following my sign...
it provides a user interface similar to Enterprise Manager with all the
facilities to edit and maintaining jobs, viewing job history, ....
as the Developer Edition ($49.00) is not allowed to manage production
servers, this is another free and legal way to perform your desired tasks...
hth
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtm http://italy.mvps.org
DbaMgr2k ver 0.5.0 - DbaMgr ver 0.51.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
--------- remove DMO to reply

Thanks for the tips everyone. Unfortunately I would really like to
stay in the context of Access. Essentially I am trying to build a
dumbed down front end for a client to perform some basic functionality
like start an existing job and see the status of that job upon
completion with any errors. I don't need or want much of the
functionality available in Enterprise Manager thus that is why I don't
want to redistribute that. Looks like I will have to hack something
together myself.

You should consider taking Darren Green's suggestion and using SQL-NS.
You'll still have the same licensing issues you would have if you
distributed SQL EM, but you can code your app to only use the pieces
of it that you need.

-- Mary
Microsoft Access Developer's Guide to SQL Server
http://www.amazon.com/exec/obidos/ASIN/0672319446

[quoted text, click to view]