G
Guest
Hi
I've just discovered that the Jet OLEDB Provider does not support
OleDbCommandBuilder.DeriveParameters, to discover the number and type of
parameters expected by a Microsoft Access query.
I'm a little surprised, as it was always possible to use the ADO Refresh
method with this provider to populate a Paramters collection.
Is there a reason for this? Is there a workaround?
I know that it's an expensive operation which should be avoided anyway, but
it's sometimes useful, and I'd like to use the same code against both Access
and SQL Server.
Thanks in advance.
I've just discovered that the Jet OLEDB Provider does not support
OleDbCommandBuilder.DeriveParameters, to discover the number and type of
parameters expected by a Microsoft Access query.
I'm a little surprised, as it was always possible to use the ADO Refresh
method with this provider to populate a Paramters collection.
Is there a reason for this? Is there a workaround?
I know that it's an expensive operation which should be avoided anyway, but
it's sometimes useful, and I'd like to use the same code against both Access
and SQL Server.
Thanks in advance.