RecordsetClone only retreives 100 records in ADP

[Br]

In an Access2000 project (ADP) I have a form whose recordsource is a
stored procedure in SQL. On the OnOpen event I run a simple piece of
code to move to a record based on a value on another already open form.
The code fails because the RecordsetClone is only retrieving the first
100 records. If you put a break in the code and trace through it it
works fine so it seems to be a caching issue or something.

I've found others having the same problem but didn't find a solution.
There doesn't seem to be anything about it on MS site.

Any ideas how to get Access to wait until the recordset is populated
before running the code? (Note: putting in a pause loop is not a
solution).

OnOpen()

Dim rstTemp As adodb.Recordset
Set rstTemp = Me.RecordsetClone
rstTemp.Find "[Schedule Code] = " & Forms!frmScheduleScan![Schedule
Code]
If Not rstTemp.EOF Then
Me.Bookmark = rstTemp.Bookmark
End If
--
regards,

Bradley

A Christian Response
http://www.pastornet.net.au/response

[pietlinden]

stick a DoEvents command in there to force it to finish before going on
to the next line?
------------------------------------------------------------------
"pay no attention to the man behind the curtain"

[Br]

pi********@hotmail.com wrote:

stick a DoEvents command in there to force it to finish before going
on to the next line?

That is one of the things that had been suggested before. It doesn't
have any effect.

Things I've tried include:
- DoEvents
- moving to last/first record
- if RecordCount = 100 go and get the RecordsetClone again
- Me.Requery/Me.Refresh
--
regards,

Bradley

A Christian Response
http://www.pastornet.net.au/response

[lylefair]

Br@dley wrote:

In an Access2000 project (ADP) I have a form whose recordsource is a
stored procedure in SQL. On the OnOpen event I run a simple piece of
code to move to a record based on a value on another already open form.
The code fails because the RecordsetClone is only retrieving the first
100 records.

A solution is to open an ADP recordset and to set the form's recordset
to that. This is not appreciably slower than using a recordsource
string.

The topic is discussed in
http://groups.google.ca/group/comp.d...6d7ed38ae217d8

[Br]

ly******@yahoo.ca wrote:

Br@dley wrote:

In an Access2000 project (ADP) I have a form whose recordsource is a
stored procedure in SQL. On the OnOpen event I run a simple piece of
code to move to a record based on a value on another already open
form. The code fails because the RecordsetClone is only retrieving
the first 100 records.

A solution is to open an ADP recordset and to set the form's recordset
to that. This is not appreciably slower than using a recordsource
string.

The topic is discussed in
http://groups.google.ca/group/comp.d...6d7ed38ae217d8

It'd be good to know why it happens. We have it happen on a few forms in
different systems. Some start working again for no noticeable reason,
some we didn't notice weren't working because they hadn't hit the 100
records mark, others never have a problem yet run almost identical code.
I thinkwe've also had it happen in comboboxes.

I think for me the best solution is to redesign the interface. Instead
of calling up the form with the full dataset and moving to the record I
want I will open the form with just that record. I'll then use a
seperate form for adding new records. In the end that'll be better for
the users anyway.
--
regards,

Bradley

A Christian Response
http://www.pastornet.net.au/response

[Br]

ly******@yahoo.ca wrote:

Br@dley wrote:

In an Access2000 project (ADP) I have a form whose recordsource is a
stored procedure in SQL. On the OnOpen event I run a simple piece of
code to move to a record based on a value on another already open
form. The code fails because the RecordsetClone is only retrieving
the first 100 records.

A solution is to open an ADP recordset and to set the form's recordset
to that. This is not appreciably slower than using a recordsource
string.

The topic is discussed in
http://groups.google.ca/group/comp.d...6d7ed38ae217d8

It'd be good to know why it happens. We have it happen on a few forms in
different systems. Some start working again for no noticeable reason,
some we didn't notice weren't working because they hadn't hit the 100
records mark, others never have a problem yet run almost identical code.
I thinkwe've also had it happen in comboboxes.

I think for me the best solution is to redesign the interface. Instead
of calling up the form with the full dataset and moving to the record I
want I will open the form with just that record. I'll then use a
seperate form for adding new records. In the end that'll be better for
the users anyway.
--
regards,

Bradley

A Christian Response
http://www.pastornet.net.au/response

[lylefair]

Br@dley wrote:

ly******@yahoo.ca wrote:

The topic is discussed in
http://groups.google.ca/group/comp.d...6d7ed38ae217d8

It'd be good to know why it happens.

Did you read the referenced thread?

[lylefair]

Br@dley wrote:

ly******@yahoo.ca wrote:

The topic is discussed in
http://groups.google.ca/group/comp.d...6d7ed38ae217d8

It'd be good to know why it happens.

Did you read the referenced thread?

[Br]

ly******@yahoo.ca wrote:

Br@dley wrote:

ly******@yahoo.ca wrote:

The topic is discussed in
http://groups.google.ca/group/comp.d...6d7ed38ae217d8

It'd be good to know why it happens.

Did you read the referenced thread?

I read the post the link pointed to.....
--
regards,

Bradley

A Christian Response
http://www.pastornet.net.au/response

[Br]

ly******@yahoo.ca wrote:

Br@dley wrote:

ly******@yahoo.ca wrote:

The topic is discussed in
http://groups.google.ca/group/comp.d...6d7ed38ae217d8

It'd be good to know why it happens.

Did you read the referenced thread?

I read the post the link pointed to.....
--
regards,

Bradley

A Christian Response
http://www.pastornet.net.au/response