I just worked it out - I didn't have all of the tables in the join partitioned on the same scheme - I was missing one. So I guess the...

HEEEEYY!!! It's funny how it all snaps into focus once you get past those mundane details! 🙂 I knew it was something rediculous I was missing...

Thanks!

This is probably a rediculous question, but how can any of your "using the tally table" examples work if you don't declare N? I guess I just don't see...

In point of fact, I actually wrote a sketchy, cumbersome, client-side loop to "calculate" the date that materials needed to be ordered based on the date they were needed for...

Arrrgh...  And to think I spent half a day writing a sketchy, cumbersome client-side loop to get this exact value for an insert statment... *sigh*

Clearly the writer is knowledgable, but this cat definitely needs a proofreader or a ghost-writer or something...  Very hard to understand and follow at times. 

That's my primary motivation for doing it in the database.  That, and the fact that backing up the database covers all the bases, and there's only one "space issue" to...

That's a great idea, except that adding tables is not an option.  This needs to be a read only kind of query.  You said that there's a way you could...

Yes, there are any number of ways to get where I'm going, and I already have workarounds.  At this point, I'm mostly just frustrated because this is a classic case...

I'm with you... But instead of selecting * in that last line, select only the new field - shouldn't make a difference, right?

Thus:

select top 0 * into #MyTable...

No, I tried that too.  It didn't seem to have any effect on the situation.  Any other ideas?

Thank you all for your ideas! We'll see how it goes...

Excellent. That did the trick. But is there anything I can tell these guys to do when importing from access to prevent their id's from being specifically associated...

That last one did it. Thank's a lot guys!