Sorry, I didn't check my post and I submitted it... I had included backslash n and apparently, it didn't take on this forum....

Have you tried backslash n ??

(and, now you...

You...

*= is severely deprecated and may produce unexpected results. Don't use it.

Have you tried using SELECT/INTO using QUOTENAME for each column?

Heh... now THAT's entertainment 😀 Would have loved to see their faces...:w00t:

So post what you've tried so we can coach you...

Ugh! A "Sequence" table... I hate 'em... If you don't already hate 'em, you will.;)

Ok, David... let's pretend that the following is what your 3rd party sequence table looks...

You don't appear to have anything to relate the given values to logical rows... have you posted all the columns that appear in these tables?

The system has to be able to see the file to load it... make sure SQL Server Services use a startup account that can see the path to the file.

Heh... did you convert the correct column? Only way you can get that error is if the target column is actually an INT... double check the schema and make...

I think you would be unhappy... unless there's a pot wad of extra money involved... in which case, you'll still be unhappy but more satisfied 😉

What are you using to determine the size of the table?

No... I'd think not. What kind of "fields" are you talking about? Parameters from some GUI or columns in a table? Why wouldn't you know that max...

This looks like homework... I'd recommend that you post what you've tried so we can help you learn...

SQL Server also has Global Temp tables (##) which are a bit different than regular (#) temp tables.

The real key, though, is that you may be doing something wrong in...