Don't cross post. Post for the correct version and stop.

Answered here: http://www.sqlservercentral.com/Forums/Topic558880-146-1.aspx

Matthew,

It's one thing to go to 2-3 servers, and another to go to 50. If you have 50, then it could easily be 30 or 100 in a year, so...

Look for any entries prior to this. It's a generic error, so likely something else was logged before this.

you've got two things to weigh. First is the Access front end, which probably is fine. Rewriting it in C# would probably be a good learning experience, and great writing/blog...

Don't think this is stored anywhere. How do you do the index? Maintenance plan? Typically there are logs setup for those.

Each left join is creating more and more work. Not sure what you can do here since it looks like the structure doesn't lend itself to easy reporting.

What's the indexing...

Is it time for each section added or time from first to last timestamp for each employee?

You might need to built a CTE to grab all the times and then...

Graeme,

Nicely put. Being too competitive is as problematic as not enough, but I do agree that this next generation sees a little too much "evenness" across the board.

I know every...

I wish you'd been out here! That was some adventure, but it turned out OK. Horse is still alive, about 9 days now.

Please post in the appropriate forum. Moved to the Reporting Services, Report Development forum.

Please don't double most. Lots of people check all forums.

Answered here: http://www.sqlservercentral.com/Forums/Topic558262-146-1.aspx

I don't believe that you can change versions.

Do one or the other first, not together. You're asking for issues.

The 2000->2005 item needs testing for keyword change. You can upgrade to 2005, running in 80 compatability mode, which...

I don't think you can do this dynamically directly from a job. You can call a stored proc in the job, build the parameter in the proc and call xp_cmdshell,...

This is called a crosstab report. Search for that.