Max Records in ADP form

  • Thread starter Thread starter Peter Crickman
  • Start date Start date
P

Peter Crickman

In an Access 2000 .adp front-end over a SQL Server 2000 backend, a form's
MaxRecords property is set to 1000 in Design Mode. When the form is
initially loaded, the MaxRecords is set to 1 and the first record is
displayed to the user. A filter textbox is used to limit the records
retrieved on the form. When the user enters a filter, the click event code
updates the ServerFilter property to the appropriate WHERE clause and the
form's MaxRecords value is set to 0 and the form's recordsource is
refreshed. The form's record selector shows the correct number of maximum
records for the entered filter (>19,000 in this case). However, when the
user clicks on the max record selector (>|) button, the form appears to
momentarily skip ahead to the proper record and then reverts back to the
current record (before the button was pressed).

Similarly, if I move to the 1000th record (by typing 1000 in the record
number field in the selector) and then try to move forward to the 1001st
record the form stays on the 1000th record.

What produces this behavior? Why isn't the overridden MaxRecords form
property allowing the form record selector to move ahead to the proper
record.

Peter
 
It's an option you have to set
Click on Tools > Options then the Advanced tab to get to the Default Max Records


----- Peter Crickman wrote: ----

In an Access 2000 .adp front-end over a SQL Server 2000 backend, a form'
MaxRecords property is set to 1000 in Design Mode. When the form i
initially loaded, the MaxRecords is set to 1 and the first record i
displayed to the user. A filter textbox is used to limit the record
retrieved on the form. When the user enters a filter, the click event cod
updates the ServerFilter property to the appropriate WHERE clause and th
form's MaxRecords value is set to 0 and the form's recordsource i
refreshed. The form's record selector shows the correct number of maximu
records for the entered filter (>19,000 in this case). However, when th
user clicks on the max record selector (>|) button, the form appears t
momentarily skip ahead to the proper record and then reverts back to th
current record (before the button was pressed)

Similarly, if I move to the 1000th record (by typing 1000 in the recor
number field in the selector) and then try to move forward to the 1001s
record the form stays on the 1000th record

What produces this behavior? Why isn't the overridden MaxRecords for
property allowing the form record selector to move ahead to the prope
record

Pete
 
This option is set to 30,000. I don't think it is directly affecting this
problem. The problem appears to be tied to the MaxRecords originally set in
the form. Why can't it be overwritten in form code?




It's an option you have to set.
Click on Tools > Options then the Advanced tab to get to the Default Max
Records.


----- Peter Crickman wrote: -----

In an Access 2000 .adp front-end over a SQL Server 2000 backend, a
form's
MaxRecords property is set to 1000 in Design Mode. When the form is
initially loaded, the MaxRecords is set to 1 and the first record is
displayed to the user. A filter textbox is used to limit the records
retrieved on the form. When the user enters a filter, the click event
code
updates the ServerFilter property to the appropriate WHERE clause and
the
form's MaxRecords value is set to 0 and the form's recordsource is
refreshed. The form's record selector shows the correct number of
maximum
records for the entered filter (>19,000 in this case). However, when
the
user clicks on the max record selector (>|) button, the form appears to
momentarily skip ahead to the proper record and then reverts back to
the
current record (before the button was pressed).

Similarly, if I move to the 1000th record (by typing 1000 in the record
number field in the selector) and then try to move forward to the
1001st
record the form stays on the 1000th record.

What produces this behavior? Why isn't the overridden MaxRecords form
property allowing the form record selector to move ahead to the proper
record.

Peter
 
Back
Top