Filter of Datasheet (disconnected ADO recordset) error

[Corey-g via AccessMonster.com]

Hi All,

Using: A2K3 - WinXP Pro - Oracle 9i

I have a form that displays a full listing of an Oracle table in datasheet
view using a disconnected ADO recordset. This works as expected - I can see
and traverse all of the data, and I can update / edit / delete records just
fine (and see the changes in the Oracle back-end).

Now when I try to use the built in filtering (right-click - 'filter by' or
'filter excuding' etc...) I get a "Data provider could not be initalized'
error msg when trying to remove the filter (seems that it will filter okay
for one field, then another by overriding the first, but I can't seem to
'chain' them together either). What I mean is if I filter on one field, then
right-click and filter on the next field, the first filter is replaced with
the second, and not a sub-set from both filters)

I did try to find info about this by searching here and googling it, but all
I could find was that most thought this wouldn't work, and someone suggested
using the 'ApplyFilter' event, but I couldn't find anything on what to do in
the event that would help to filter / unfilter the datasheet.

Any help would be appreciated,

Corey

 

[Corey-g via AccessMonster.com]

Anybody have anything (links, books, tutorilas, etc...) with more information
regarding this at all?

I can't even test different approaches very well as it's causing access to
crash every time I try to return to design view. I get the feeling that
using the 'right-click' method is not usable for unbound forms and
disconnected recordsets. So if this is in fact the case, is it possible to
not show these functions (filtering)when a user right-clicks?

Thanks again,

Corey

 

[Corey-g via AccessMonster.com]

Hi Again,

Still trying to figure out what is going on here, and all I can come up with
is that these right-click funtions are 'normally' DAO actions - not for ADO.
Or is it that when I try to use them on the form, I am either trying to
filter the form (not the recordset).

If Access would stop crashing after the 'Data Provider could not be
initialized' error message, I might be able to figure out what's going on...

Is there a way to determine what action the user is trying to do, and
implement this in code so that it doesn't crash? Or again, a way to disable
this so that I can build me own filtering?

Corey