Query is too complex and OleDbCommandBuilder

[John]

I have a MS Access 2000 database table which has a large number fields. I am
using the OleDbCommandBuilder to generate the SQL update command. The
problem I now have is that the auto generated update Command is too large
and fails with the following error "Query is too complex".

The problem is caused because the OleDbCommandBuilder uses Optimistic
Concurrency and this generates a long SQL update command which checks if the
record on the database has been modified.

Is there any quick way to remove the concurrency checks as I don't need to
do this?

Thanks

 

[Mary Chipman]

You're going to continue to have problems no matter what you do as
long as that table has too many fields because you can't change the
built-in behavior of the command builders. Your best option is to
partition the table in to two or more tables with a one-one
relationship. If that's not possible, then I'd suggest not using
command builders. You may be able to work around the too-many-fields
problem by hand-coding your data access.

--Mary