That did work well! I didnt even know about views in SQL until now. Thanks for that
so this part works now
ALTER PROCEDURE [dbo].[sp_Issue_GetIssuesB
@ProjectId int,
@UserId int
AS
BEGIN
SET NOCOUNT ON;
SELECT *
FROM dbo.IssueView
END
But errors crop up when I try to add a 'where' clause
ALTER PROCEDURE [dbo].[sp_Issue_GetIssuesB
@ProjectId int,
@UserId int
AS
BEGIN
SET NOCOUNT ON;
SELECT *
FROM dbo.IssueView
WHERE tbl_Issues.IssueCreatorId=
AND tbl_Issues.ProjectId=@Proj
ORDER BY tbl_Issues.IssueId DESC;
END
Errors read:
Msg 4104, Level 16, State 1, Procedure sp_Issue_GetIssuesByReleva
The multi-part identifier "tbl_Issues.IssueCreatorId
Msg 4104, Level 16, State 1, Procedure sp_Issue_GetIssuesByReleva
The multi-part identifier "tbl_Issues.ProjectId" could not be bound.
Msg 4104, Level 16, State 1, Procedure sp_Issue_GetIssuesByReleva
The multi-part identifier "tbl_Issues.IssueId" could not be bound.
Can you please suggest a way out as creating a view would be of no use if this doesnt work
Main Topics
Browse All Topics





by: debuggerauPosted on 2008-03-26 at 18:35:18ID: 21217921
Since access does not contain views, I suggest to create another query as its replacement, however your code functions may need modifying as a result.
library/de fault.asp? url=/libra ry/ en-us/d nacc2k/htm l/acadvsql .asp
http://msdn.microsoft.com/
look under the heading views...