I'm not sure the poster actually needs dynamic SQL. If done the way his code suggested, then yes, dynamic SQL would be required, because SQL doesn't allow you...

Just in case there's a value to the concept, I thought I'd describe how things were set up at one place I did some SSRS work:

They had multiple databases, but...

Perhaps the larger issue is the value of numbers being generated based on a prediction, especially when combined with "real" numbers. I don't mean to come across as...

Fantastic! I'll look forward to seeing what you have. Thanks!

Steve

(aka smunson)

:-):-):-)

dtcalif (8/12/2009)

---

I am in the process of creating a simple routine which will parse the .QFX...

I hate to be the bearer of bad news, but once you go down the road of what effectively amounts to "dynamic SQL", almost everything you do with the results...

I hear ya... supporting legacy mistakes is always a PITA, but somehow, it always has to get done. I've never hated Access though... it's a darn...

That's beautious, Jeff... I liked it so much I decided to make a stored procedure out of it, that's customizable on how many numbers you get, along with...

I know you said "don't ask" with respect to Access 95, but seriously, you DO need to consider at least the possibility of at least moving to Access '97, where...

Why isn't this code in a stored procedure instead of a view? If you need to be able to substitute an actual datetime value for each occurrence of...

One question - you want to validate the input, so is there a master data source to check it against, or you just looking to validate that a numeric field...

There's one curiousity about your code you'll need to resolve, and it's associated with the data type of the PartnerID column of dbo.MatterMaster. You want to set it...

You may be one of perhaps very few that use SQL Server with PHP instead of MySQL, which is significantly more common as a combination. I've heard...

I think you're right about the OCD. I've been known to do that from time to time, and in this case, I doubt it's necessary. ...

Ok, here's the quick version. It's not exactly what you asked for, but it may more clearly represent your "occurrences":

DECLARE @LOG_TABLE AS TABLE(

RECNUM int IDENTITY(1,1),

Emp_ID int,

Start_Entry DateTime,

End_Entry DateTime,

FName...

Now we're dealing with an entirely new problem. By abandoning the count, we can't use the GROUP BY quite the same way, so it's not a simple change...