Handle in terms of what ? SQL Server doesn't work like
Access - maybe that's where you are going with that. If you
use the default isolation level, you should be fine. Or are
you having problems with blocking, locking? If that's the
case, the linked tables can hurt - especially when users
open tables directly. You want to make sure the client side
is consuming the entire recordset/result set so that the
locks are released. Make your transactions as short and fast
as possible and avoid cursor. Implement appropriate indexes.
Do you have a more specific concern?
-Sue
On Wed, 4 Jul 2007 12:14:12 +1000, "Rotsey"
<malcolm_smith (AT) RemoveThis (DOT) optusnet.com.au> wrote:
Quote:
Hi,
I have a Access 2003 talking to SQL 2005 express DB via
linked tables.
I also have .NET forms application that also talks to the
SQL DB.
I want to know how to handle concurrency in the .NET app.
I don't want to have to change the Access app though
Is there a method that would work for both Access and .NET?
Malcolm |