Hello. I have to support a vb3.0 application. As the number of users and
the volume of data has grown more than it was expected, we're thinking to
scale it up. To do that, the first step would be to migrate from access 2.0
(the underlying database) to sql server 6.5 (our available corporate
database)

    My first approach would be to link sql-server tables to ms-access
database, so the program could run without code changes.

    But the problems arise. If we trace the communication between the
application and sql-server, we see that:

PROBLEM 1
----------------------------------------
- updates are made in this way:

        UPDATE table SET fld1 = val1
        WHERE fld1=v1 AND fld2=v2 AND fld3=v3 AND fld4=v4 AND SO ON...

instead of:

        UPDATE table SET fld1 = val1
        WHERE fld1=v1

being <fld1> the main key.

Is there any way of changing this behaviour? Note that:

- it is unconvenient because some of the tables have more than 100 fields,
so     the SQL created is veery unefficient.
- it is unconvenient because the application is running in a multi-user
environment, and we'd like all changes in fields to be visible inmediately.

PROBLEM 2
-----------------------------
The application has one true-grid, intended to be updated each 10 seconds.
It relys on a data-control, to get the information from the database.

But the data-control creates a stored-proc as a fashion of cursor, and
employs it to iterate over the data.

For this kind of operation, it's extremely slow.

Does anybody know how can we change it?