Man, Steve, I want your job! 

That is correct zzx375, it looks to me as though Reporting Services doesn't support print subscriptions.

Yes, I have 2 records with ProviderNumber = 105; but that is because ProviderNumber and Facility together comprise the primary key. 

Like Ninja said, my problem was an update trigger...

Ninja's,

I had not thought of a trigger.  Good idea!  I found triggers, one involved with updating the table.  It is a long trigger, written back in 1998 by a developer...

A good article, Janet!  I've had bad managers, and good managers.  I realize that I probably haven't has managers as bad as your ugly managers.

One comment; I think the influences...

Steve,

Who does your wife work for?  4 weeks vacation!  Fantastic!!!

I'll be taking off time starting next Wednesday (the 13^th) and going through until January 2^nd.  I'm looking forward to it,...

Hi Lisa,

I'll try to be clearer.  The ASP.NET application is on our web server, and that server is the only server outside of our firewall, so that it might be...

I've got a follow-up question about this. The ASP.NET application uses SSL, and the Reporting Services report is on a different server, behind our forewall. When I ran the report from home...

Hello Lisa,

OK, I've been experimenting and I am really not getting this.  It might be best if I work through an example.

Let's suppose my report is called ProviderData.  It has...

Ray,

So, what you're saying is taht all Reporting Services reports get published to http://servername/reportserver, so that they can be run from http://servername/reports, correct?

And if I may ask another...

Ninja's,

I got the error when I attempted to open (view) the job history.  I've no idea if it is in the history or not.

Oh, I see.  OK.  Because of the original error message, the name of the job should be "Backup_SystemDBs_Weekly".  I have no idea why the job name was missing the beginning...

Sorry I didn't reply earlier.  We were experiencing network connectivity problems last week Friday.

Anyway, why is it you believe that renaming the job will help?

What do I do?  Call them up and say something like, "I think I've found a bug in SSMS, can you verify this for me, please?" or something like that?

Ninja,

You wrote:

Select IDCol FROM dbo.MyTable WHERE ISNULL(Col1, '') <> ISNULL(CONVERT(VARCHAR(newsize)), '')

What I am not following is the condition in the WHERE clause:

ISNULL(Col1, '') <> ISNULL(CONVERT(VARCHAR(newsize)), '')

What are you accomplishing...