Advertisement

02.19.2007 at 09:26PM PST, ID: 22400182
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

9.2

The multi-part identifier "..." could not be bound.

Asked by smacca in SQL Server 2005

Tags: , ,

Hi,

Can someone help me as to why the following SQL is cause the error:

   "The multi-part identifier "..." could not be bound."

Thanks.

---------------------------------

--region [dbo].[SelectPagedAccountsByAccountID]

------------------------------------------------------------------------------------------------------------------------
-- Procedure Name: [dbo].[SelectPagedAccountsByAccountID]
-- Date Generated: Tuesday, 20 February 2007
-- Author:         Stephen McCormack - stephenm@mwebsolutions.com.au
-- Company:        MWeb Solutions Pty Ltd
-- Software:            CodeSmith v4.0.0.0
-- Template:       StoredProcedures.cst
-- Comments:       'Custom Paging in ASP.NET 2.0 with SQL Server 2005' - http://aspnet.4guysfromrolla.com/demos/printPage.aspx?path=/articles/031506-1.aspx
--------- --------------------------------------------------------------------------------------------------------------

CREATE PROCEDURE [dbo].[SelectPagedAccountsByAccountID]

      -- paging parameters
      @PageNumber int = 1 ,
      @PageSize int = 10 ,

      -- index column(s)
      @AccountID int,
      
      -- sort expressions
      @SortBy varchar(50) = 'CreatedDate' ,
      @SortDirection varchar(4) = 'DESC'
      
AS

      -- turn off rows affected
      SET NOCOUNT ON
                  
      --isolation level
      SET TRANSACTION ISOLATION LEVEL READ COMMITTED

      -- system function stores
      DECLARE
            @ErrStatus int,       -- stores error status
            @RowsAffected int      -- stores number of rows affected

      -- parameter validation
      IF (@PageNumber < 1)      SET @PageNumber = 1
      IF (@PageSize < 1)            SET @PageSize = 10

      ----------------------------------------------------
      -- Determine start and end row index.
      ----------------------------------------------------  
      DECLARE
            @StartRowIndex int,       -- the starting row index
            @EndRowIndex int            -- the ending row index
            
      SET @StartRowIndex = (@PageNumber-1) * @PageSize
      SET @EndRowIndex = (@StartRowIndex + @PageSize)-1

      ----------------------------------------------------
      -- Select Paged Set
      ----------------------------------------------------
      SELECT
            [RowNum],
            [dbo].[Accounts].[AccountID], /* pk */
            [dbo].[Accounts].[CustomerID], /* fk */
            [dbo].[Customers].[Name] AS [CustomerName], /* fk name column */
            [dbo].[Accounts].[DiscountAmount],
            [dbo].[Accounts].[DiscountRate],
            [dbo].[Accounts].[DiscountCode],
            [dbo].[Accounts].[Notes],
            [dbo].[Accounts].[CreatedDate],
            [dbo].[Accounts].[CreatedBy],
            [dbo].[Accounts].[ModifiedDate],
            [dbo].[Accounts].[ModifiedBy]
      FROM
      (
            SELECT
                  [dbo].[Accounts].[AccountID], /* pk */
                  [dbo].[Accounts].[CustomerID], /* fk */
                  [dbo].[Customers].[Name] AS [CustomerName], /* fk name column */
                  [dbo].[Accounts].[DiscountAmount],
                  [dbo].[Accounts].[DiscountRate],
                  [dbo].[Accounts].[DiscountCode],
                  [dbo].[Accounts].[Notes],
                  [dbo].[Accounts].[CreatedDate],
                  [dbo].[Accounts].[CreatedBy],
                  [dbo].[Accounts].[ModifiedDate],
                  [dbo].[Accounts].[ModifiedBy]
                  ,
                  ROW_NUMBER() OVER
                  (
                        ORDER BY
                              [dbo].[Accounts].[CreatedDate] DESC
                  ) AS [RowNum]
            FROM
                  [dbo].[Accounts]
                  INNER JOIN [dbo].[Customers] ON [dbo].[Accounts].[CustomerID] = [dbo].[Customers].[CustomerID]
            WHERE
                  [dbo].[Accounts].[AccountID] = @AccountID
      ) AS [PagedSet]
      WHERE
            [RowNum] BETWEEN @StartRowIndex AND @EndRowIndex      
                  

      -- check for errors
      IF @ErrStatus <> 0
      BEGIN
            RAISERROR( 'Error occurred in stored procedure ''[dbo].[SelectPagedAccountsByAccountID]''', 10, 1 )
            RETURN @ErrStatus
      END

      -- ensure correct number of rows affected
      IF @RowsAffected > @PageSize
      BEGIN
            RAISERROR( 'Unexpected number of rows affected by stored procedure ''[dbo].[SelectPagedAccountsByAccountID]''', 10, 1 )
            RETURN -999 -- standardised return code for this - 'Unexpected rowcount'      
      END
      
      ----------------------------------------------------
      -- RecordCount Resultset
      ----------------------------------------------------  
      SELECT
            COUNT(*) AS [RecordCount]
      FROM
            [dbo].[Accounts]
            
      /* must use single statement immediately to store system functions
      as all DML statements, SELECT, IF, PRINT and SET will reset @@error to zero */
      SELECT
            @ErrStatus = @@ERROR

      -- check for errors
      IF @ErrStatus <> 0
      BEGIN
            RAISERROR( 'Error occurred in stored procedure ''[dbo].[SelectPagedAccountsByAccountID]''  when returning the total number of records.', 10, 1 )
            RETURN @ErrStatus
      END

      
      -- turn on rows affected
      SET NOCOUNT OFF

      -- success(0)
      RETURN 0
      
--endregion

GO
Start Free Trial
[+][-]02.19.2007 at 09:55PM PST, ID: 18568620

View this solution now by starting your 7-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

 

About this solution

Zone: SQL Server 2005
Tags: identifier, could, bound
Sign Up Now!
Solution Provided By: aneeshattingal
Participating Experts: 3
Solution Grade: A
 
 
[+][-]02.19.2007 at 10:03PM PST, ID: 18568641

At Experts Exchange, members can ask their questions to thousands of technology professionals, also known as Experts. Experts compete and collaborate to answer those questions by leaving comments like this one.

Start your 7-day free trial to view this Expert Comment or ask the Experts your question.

 
[+][-]02.19.2007 at 10:05PM PST, ID: 18568649

At Experts Exchange, members can ask their questions to thousands of technology professionals, also known as Experts. Experts compete and collaborate to answer those questions by leaving comments like this one.

Start your 7-day free trial to view this Expert Comment or ask the Experts your question.

 
[+][-]02.19.2007 at 10:08PM PST, ID: 18568658

At Experts Exchange, members can ask their questions to thousands of technology professionals, also known as Experts. Experts compete and collaborate to answer those questions by leaving comments like this one.

Start your 7-day free trial to view this Expert Comment or ask the Experts your question.

 
[+][-]02.19.2007 at 10:48PM PST, ID: 18568782

At Experts Exchange, members can ask their questions to thousands of technology professionals, also known as Experts. Experts compete and collaborate to answer those questions by leaving comments like this one.

Start your 7-day free trial to view this Expert Comment or ask the Experts your question.

 
 
Loading Advertisement...
20080716-EE-VQP-32