H
Hoffmann Andreas
Our company developing an Access Solution, we work the most time with Access.
Our Customers use our product the most time of there daily work and the Mount
of Data is rising up very quickly. The important working table has more than
128000 Rows (like Customers or Products).
For editing we use a Form and bind it to a Query. The Amount of the Rows is
more than 1300000 rows.
If the Count of Rows in a Form is greater than around 128000 rows,
forms.Recordset.findfirst find a Row (check with recordset.noMatch) but the
Form doesn't noticed that the Data in the Recordset is changed and showed the
content of another Row. The Cursor Position is at 13000, not at 128xxx.
In some cases the Data (row >128000) is display valid, but after changing
the Datarow, another (with a lower Position) will be override.
I hope I describe the Problem fully understandable.
If there any Questions, you can contact me.
Greets from Austria
Andreas Hoffmann
Our Customers use our product the most time of there daily work and the Mount
of Data is rising up very quickly. The important working table has more than
128000 Rows (like Customers or Products).
For editing we use a Form and bind it to a Query. The Amount of the Rows is
more than 1300000 rows.
If the Count of Rows in a Form is greater than around 128000 rows,
forms.Recordset.findfirst find a Row (check with recordset.noMatch) but the
Form doesn't noticed that the Data in the Recordset is changed and showed the
content of another Row. The Cursor Position is at 13000, not at 128xxx.
In some cases the Data (row >128000) is display valid, but after changing
the Datarow, another (with a lower Position) will be override.
I hope I describe the Problem fully understandable.
If there any Questions, you can contact me.
Greets from Austria
Andreas Hoffmann