Rick is exactly right. You can't manage jobs, nor maintenance plans with SSMS Express.

The expression should be in the color property for the column, I was under the impression that RS uses aliases, like "Blue", "Red", "Green" for colors instead of HTML colors.

Try:

Iif(datediff("d",Parameters!Date.Value,now())>28,"Red","Blue")

Good...

Work around:

Link Access db via a linked server to SQL Server.

Set SQL Server as datasource.

The query will connect to Access through SQL Server at report run time.

Always good to answer...

I created my own job monitoring script by modifying a similar script I found on this site. I basically created a table to hold all of the job information...

I always use #temp_tables to hold arrays for my stored procedures. There's probably a better way, but it does the trick.

SQL Mail problem check:

Look at your Internet Settings,(Setttings->Control Panel->Internet Options) your default mail client might be set to Outlook Express. Make sure this is set to Outlook.

Have you tried the Database Mail feature for 2005. I have a 64 bit SQL server so I can't use SQL Mail, but I can use Database Mail. ...

Was SQL Server Agent restarted after setting up SQL Mail?

I have found the internet to be my best resource for learning T-SQL. I will identify the command I need to use in some code and google t-sql 'command'...

I don't know of a server role that would provide the type of permissions you are requesting, but you can use database roles.

Select the db_datareader and db_datawriter database...

I recieved the error because I wasn't calling the stored procedure correctly.

Thank You SO much Todd!

I get an error when attempting to call those stored procedures, even from the server. Maybe they have been depreciated for SQL Server 2005?

Thanks,

jim

Definitely can't view/edit SQL Server Agent Jobs.

How about maintenance plans?

Thanks,

jim

I think that one must update the 2000 stored procedures to be 2005 compliant. Look up update SQL Server 2000 stored procedures in BOL.

You might also check out this...

The error specifies that the transaction log for BossData is full.

I've found the best means for fixing this problem is.

1. Set the DB in to simple recovery mode.

2.Do a full...