Recordset Limitation

Report · May 13, 2007

Hi. We have a page that pulls down records from an Access Database. This database has more than 125 records but when paging through we only get to 125 and then nothing. I know the record 126 is there but the asp page displayed via the browserr will not allow it to be seen. Very odd. Any clues as to where to start. I wonder if access has some kind of restriction when the server tries to pull off all the data in one go?
Regards
Paul
paul@fdpmedia.com

Report · May 13, 2007

I would do a view source on your page and see if there is an issue with some
data preventing the display as Access is capable of showing way more than
125 records.

--
Paul Whitham
Certified Dreamweaver MX2004 Professional
Adobe Community Expert - Dreamweaver

Valleybiz Internet Design
www.valleybiz.net

"FissDesign" <webforumsuser@macromedia.com> wrote in message
news:f27k1u$e0u$1@forums.macromedia.com...
> Hi. We have a page that pulls down records from an Access Database. This
> database has more than 125 records but when paging through we only get to
> 125
> and then nothing. I know the record 126 is there but the asp page
> displayed via
> the browserr will not allow it to be seen. Very odd. Any clues as to where
> to
> start. I wonder if access has some kind of restriction when the server
> tries to
> pull off all the data in one go?
> Regards
> Paul
> paul@fdpmedia.com
>

Report · May 13, 2007

Have you tried paging through your records? Try splitting them up via paged records and see if that works.

Also have you set a restriction on how many records the repeat region is allowed to display?

Hope that helps,

Report · May 14, 2007

Thank you everyone. Very odd. I have even tried creating a blank asp page and a new recordset with no paging. Here is the code below minus the HTML elements.

<%@LANGUAGE="VBSCRIPT" CODEPAGE="1252"%>

<%
Dim rstest
Dim rstest_numRows

Set rstest = Server.CreateObject("ADODB.Recordset")
rstest.ActiveConnection = MM_IPDConn_STRING
rstest.Source = "SELECT * FROM Clientcontacts"
rstest.CursorType = 0
rstest.CursorLocation = 2
rstest.LockType = 1
rstest.Open()

rstest_numRows = 0
%>
<%
Dim Repeat1__numRows
Dim Repeat1__index

Repeat1__numRows = -1
Repeat1__index = 0
rstest_numRows = rstest_numRows + Repeat1__numRows
%>

<body>
<%
While ((Repeat1__numRows <> 0) AND (NOT rstest.EOF))
%>

<%
Repeat1__index=Repeat1__index+1
Repeat1__numRows=Repeat1__numRows-1
rstest.MoveNext()
Wend
%>

</body>
</html>
<%
rstest.Close()
Set rstest = Nothing
%>

And I opened up the database in Access and the records not showing are there. I cannot see why a simple asp page with no filter, no paging, nothing but a table sourcing the entries does not show the entire list. Could the ISP have a restriction of more than 125 entries being accessed in one go.

Paul

Report · May 14, 2007

> And I opened up the database in Access and the records not showing are
> there.
> I cannot see why a simple asp page with no filter, no paging, nothing but
> a
> table sourcing the entries does not shwo the entire list. Could the ISP
> have a
> restriction of moer than 125 entries being accessed in one go.
>

It may be the data itself. For instance, if you output a < or some other
reserved character without encoding it as < (or whatever), then it could
appear that data is not there when it is. (IOW - use Server.HTMLEncode
wherever such characters may occur.) Also, if some error occurs in a part
of the HTML that does not render, the error message would only be visible
when you do a view source on the page.