Got the same result... no error but no change.  Thank you for trying.

>(select count(*) from myview where ...) as field1

>(select sum(field) from my where ...) as field2

Your last post said that you used aggregate functions for each field.  Looking at the code...

First, thank you for the table and data code...  always a pleasure to NOT have to write code just to do a test setup...

Your problem, I believe, is with the following section of code...

A.zcmSBA_V_SUBSTATIONID=B.zcmSBA_V_SUBSTATIONID AND

  A.zcmSBA_V_WONO=B.zcmSBA_V_WONO AND

  A.zcmSBA_N_JONO=B.zcmSBA_N_JONO AND

  A.zcmSBA_V_TRXNO=B.zcmSBA_V_TRXNO

 

Looks more like part of a WHERE clause... anyway, THAT's what...

Worse than that, it's been my experience (in SQL Server 7) that a SELECT such as yours will create a separate instance of the view, in memory, for each named instance...

Kokyan is correct... temp tables are always unique per session.  You can see the actual name of a temp table in the tree view (press f8) of Query Analyzer.  They...

Actually, there is!  It comes in the form of the PARSENAME command which was specifically developed to break apart the parts SQL object names "at the dots".  Since your example...

Thought AH did a pretty good job!

In that case, Bulk Insert has a MAX ERRORS setting that works just like the BCP -m parameter.  Again, check BOL under Bulk Insert.

No execution plan is formed for Dynamic SQL until Runtime regardless of method of execution.