Sorry I'm late with this reply...

The answer is...

.... rewrite sp_OA_portfolio_earnings to handle more than one row at a time.

Also (to add to what's already been said), you have a large number of implicit conversions that may slow things down... 1 (in code) is an implicit INT but you're columns...

Yes... I think you've done it the correct way for the right reason(s).  And such "partioning" of data is a tried and true method (although I don't care much for...

That number is correct... check in Books Online under "specifications-SQL Server objects"

Click on the Windows START button... open "ALL PROGRAMS" or some such.  Find the Microsoft SQL Server folder and click on it... find the QUERY ANALYZER icon and click on...

Please tell me you didn't add a dollar sign to some numeric data and store it as a varchar...

Gotta love embedded SQL... and not trying to be a snit about this... check out the discussing beginning to unfold at the following URL... it's similar to many other discussions...

Found another good reason not to use "parameterized scripts" as embedded SQL... see the following recent URL about the wrong execution plan being created...

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=146&messageid=373799

"Precisely"

Going back to the basics, why not just create a linked server to the Access database and use SELECT/INTO?  Will create the table and copy the data rather "automagically"...

Heh... no... they only paid me the big bucks to round UP your minutes

Why can't you change it?  Because it's 3rd party???? or ????

You're saying the format of a given text file changes a lot???  Do the text files have header information on the first line of the file?

Nope... can't be done in EM... open the view code in Query Analyzer first... save the old code... copy the code to EM... experiment with changes... copy/type the changes into Query...

That's cool... do you know if table variables still have the same fault of not being able to use statisics and not be alterable once formed?