"User!UserID" has the value I want, but how do I reference this from within a query in a dataset?

Just remembered, I can't use windows integrated security, as these credentials aren't remembered for scheduled snapshots etc. So I may need another way to pass the current user to the...

I think the way I'd like it to work is something like this:-

User opens report, data set reads any previous params from database and sets the params displayed on the...

I'm using a stored proc to produce the report. However I'm not passed this proc any params, as mentioned in my last post, the params are used for filtering within...

I'm using procs to do the query, however I've found it better to not pass params into the proc, rather have the proc return a full resultset, then let the...

Turns out this was fixed in SP1... Doh!

More fixing of my own problems...

Think I've sorted this one, for some reason I think HOST_NAME() was returning something that doesn't match my...

Sorted this now. I had to run a system stored proc to refresh/update the subscription. Found the answer on a random google result, but forgotten it now and can't for...

I'm pretty sure the identity seed was ok and didn't need reseeding. The info returned by 'dbcc checkident noreseed', showed this. The error I was getting was due to the...

Yeah, no idea what caused two constraints to crop up. Eitherway, I just figured it was using a constraint to implement the range checking. I also found a thread on...

Ok, think I found the problem, I had a rouge old check constraint in place, so when I ran sp_help on the table, I had these two rows:-

CHECK on column...

Yep, that worked a treat.

I generated a script to recreate the constraints after I had dropped them. The id's I was inserted didn't clash with any indentity ranges than...

Looks like I'm on a role in solving my own problems...

Anyway, the solution to this one, was to use HOST_NAME() instead of SERVERPROPERTY('ServerName').

Not...

Ok overcome this problem now. I was trying to use Pull Subscriptions before, so the agent was running on the subscriber. This is no good as the subscriber can't connect...

OK, so I'm replying to my own posts, bit sad, but someone else in future may find this useful.

Basically my plan of attack...