For the code example given, there is absolutely no reason to force an index... it does nothing for the code.

And, I agree, 16 column PK????  CLUSTERED???  So much for speedy...

So why did one of the BBB rows go away?  BBB only had two rows...

... and, just to be on the safe side, you should enclose the server instance name in double quotes because of the special characters it contains.

'sqlcmd -E -dWatauga_Test -SNV-DEVSQL1\DAPHNE -Q"exec SP_GENERATE_INSERTS '+@TAB_NAME+'" >>c:\myTable.sql'

Or could it simply be the special characters in the instance name that should be quoted?

LOL... I know what you mean... probably a really bad habit but the only time I normally use the ANSI "Join" statements is when an outer join is present. 

Yeowch!  When you jab someone in the eye with a sharp stick, you should at least tell them why

Guess it does help to click on the Author's name and see previous posts... especially if you remember something similar.  Thanks for identifying the dead horse, Phil.

Sam, I think step 1 would be to post you question in the Access forum.  Lots of us just don't go anywhere near Access and, as you know, the solutions...

Heh... I try to write "Fine" solutions because I've had "Mo-den-enough" with the ones that aren't   Thanks for the great compliment, Steve!

Heh... although they both have the same execution plan, I'm not sure why you wrote it as a Cross-Join that works like an Inner Join... why not just write it...

Yep...

Doh!   My bad... made an assumption  Thanks for the feedback.

LOL... I just knew I liked you for more than the code you write   I'm getting soft in my old age and...

Thanks, Vamshi... I really appreciate your feedback.