Thank you for your reply. This seems to be a design flaw. Microsoft should be able to provide read access to a diagram without granting users high level rights.

Thanks for your reply. I don't have control over the procedure being called, only the parameters being passed. I can pass as many @withmove parameters as I have data files...

The missing #4 option is almost correct. The last comparison for day should be <= to account for birthdays falling on the day you run the query.

DATEPART(d, @BirthDate) <= DATEPART(d,...

The second option is also incorrect. It's true that the second option doesn't handle leap years. I tried 03/06/1964 (today's date is 03/06/2008) and got the correct age, however put...

I tried this and it worked using one standard sql statement and one dynamic sql statement.

Declare @rc int

SET @rc = @@rowcount

If @rc > 0

BEGIN

...

That should do the trick. Good luck.

Sorry, I didn't notice that before. I would still keep the Begin End block out of the dynamic sql like the following:

SET @sql = 'SELECT ' + @ColumnName...

On the output param, try changing the if exists to a select and checking @@rowcount. If @@rowcount <> 0 set your output param.

with dynamic sql it's always a good idea to print your @sql statements to see how they would execute.

One thing I see is you are missing and end quote at the end of the SET @sql statement. The ')' isn't closed.

I agree on the post regarding using convert(char(10),mydate,101) for evaluating dates, however in this case I needed to include the time since some records have the same date portion.

Thank you for your contribution. The query you provided did the trick. Sometimes if you spend too much time thinking about a query, you end up overthinking and doing joins...