B
Bonno Hylkema
Hi there,
I have an Adp form (Acc2000) connected to a SQL Server 2000 database.
When I filter the form on area code, the resultset is for example 10 records
out of 100 records. After that I change the area code (part of the filter)
to a new value. Then the form looses its filter, 100 records are shown and
the recordnumber is an arbitrairy number, although the record itself is the
proper record.
If another field (not part of the filter) is updated, everything works fine,
the filter stays intact and shows the expected 10 records out of 100
records.
This behaviour is very confusing for the user and makes working with
filtered resultsets nearly impossible. Does anyone have a clue why this
behaviour happens and if there are any solutions or work arounds?
This behaviour does not happen in an Access mdb with the Jet data engine.
Regards, Bonno Hylkema
I have an Adp form (Acc2000) connected to a SQL Server 2000 database.
When I filter the form on area code, the resultset is for example 10 records
out of 100 records. After that I change the area code (part of the filter)
to a new value. Then the form looses its filter, 100 records are shown and
the recordnumber is an arbitrairy number, although the record itself is the
proper record.
If another field (not part of the filter) is updated, everything works fine,
the filter stays intact and shows the expected 10 records out of 100
records.
This behaviour is very confusing for the user and makes working with
filtered resultsets nearly impossible. Does anyone have a clue why this
behaviour happens and if there are any solutions or work arounds?
This behaviour does not happen in an Access mdb with the Jet data engine.
Regards, Bonno Hylkema