good day people

i tried to view the articles by putting the order from the newest to the oldest. however, after trying to edit the stored procedures, i still failed to do so...(the starter kit displays it from the oldest to the latest)

anyone has any idea?  plz help...it's very urgent...thanks a lot

Hi caleblan,

Change your storedprocedure as follows:

<code>

</code>

Once you have made this change, rebuild the site and you should be good to go.

The Stored Procedure in question is PagedAnnouncementList

hie there,

thanks for the reply, i'll try out the codes andi'll let you know the outcome later.

thanks a lot!!

hello again,

i tried the codes given above but i just realised that i already tried it before. Actually it displays it from the newest to the oldest but when it views the 2nd page or the following pages, it will view only the content of the first pages.

Let say i entered 20 items, it will only display the newest 10 articles on EVERY page.

Any idea to solve this prob? plz help

thanks again

 Hi Caleb,

The problem is that the paging functionality for the Repeater control is not intuitive, it needs to be coded and as it stands the Stored Procedure does not handle this.

The Params are hard coded right now, so basically it will always return 10 items and it will also drop 1 from page 2 or 3 etc..etc.

I am looking at this now that I have tested and recreated the problem.

But let's just say that I think the answer is to move away from a stored procedure and create a dataset, when you are doing paging with a repeater the main concern is the Start Key for the Page so when your sql executes you will get the proper results.

It is something to think about for a little while.

Ok I have fixed the issue with the NewsList and the Repeater.

You can see the results at:

http://67.164.255.166:8029/default.aspx

Now in my case, I changed it to 4 news articles per page as after testing this a little I thought that 4 is the best number otherwise the page looks cluttered.

You will have to click on the View All News Articles link to get redirected to the News_List.aspx page.

I converted the Page to use the CodeBehind Model and added proper paging through the News Articles.

Ok I have fixed the issue with the NewsList and the Repeater.

You can see the results at:

http://67.164.255.166:8029/default.aspx

Now in my case, I changed it to 4 news articles per page as after testing this a little I found 4 to be  the best number otherwise the page looks cluttered.

You will have to click on the View All News Articles link to get redirected to the News_List.aspx page.

I converted the Page to use the CodeBehind Model and added proper paging through the News Articles.

Here's another version of that procedure which will show news articles newest first. Have a look at the procedures in the aspnetdb for some examples of page type procedures, for example aspnet_Membership_FindUsersByName
Note that one uses a zero based page index.

ALTER PROCEDURE PagedAnnouncementList
(
   @pageNum INT = 1,
   @PageSize INT = 10
)
AS
-- Set the page bounds
DECLARE @PageLowerBound int
DECLARE @PageUpperBound int
DECLARE @TotalRecords int
SET @PageLowerBound = @PageSize * (@pageNum - 1)
SET @PageUpperBound = @PageSize - 1 + @PageLowerBound
-- Create a temp table to put items in the order we want
CREATE TABLE #ItemIndex
(
   IndexId int IDENTITY (0, 1) NOT NULL,
   NewsId int
)
-- Insert into temp table
INSERT INTO #ItemIndex (NewsId)
SELECT a.id
FROM announcements a ORDER BY itemdate DESC, id DESC
-- Get the goodies
SELECT a.id, a.itemdate, a.title, a.description, a.photo
FROM Announcements a, #ItemIndex i
WHERE a.id = i.NewsId
AND i.IndexId >= @PageLowerBound AND i.IndexId <= @PageUpperBound
ORDER BY itemdate DESC, id DESC
-- Return the number of pages
SELECT @TotalRecords = COUNT(*)
FROM #ItemIndex
RETURN CEILING(@TotalRecords/@pageSize)

the last one works for me  thx for the tip 

best regards

 awesome dude, thanks for the last tip, it seems to work greath now