Re: "Field cannot be updated" error with ADODataSet
From: Brian Bushay TeamB (BBushay_at_Nmpls.com)
Date: 07/01/04
- Next message: Guillermo Ortega A.: "ADO performance"
- Previous message: Brian Bushay TeamB: "Re: ADOtable Excel"
- Next in thread: Jim Albertson: "Re: "Field cannot be updated" error with ADODataSet"
- Reply: Jim Albertson: "Re: "Field cannot be updated" error with ADODataSet"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 01 Jul 2004 12:10:53 -0500
>>>scenario
>Multi-user access to the shared database
>Problem: the application sort of locks up when
>attempting to browse if more than one user is
>connected after an edit / post is made to the
>table(s).
>
>You mean optimistic locking is okay for
>multi-user?
Optimistic locking is preferred it uses a less database resources.
What is it about your application and multi user that makes you think you need
to use pessimistic locking?
>Could you suggest links where I can find info on
>Delphi <-> ADO (specifically Access / JET)
>multi-user programming / best practices?
I don't have anything for that scenario maybe someone else can point you to a
link.
>Thanks in advance,
>JA
>
-- Brian Bushay (TeamB) Bbushay@NMPLS.com
- Next message: Guillermo Ortega A.: "ADO performance"
- Previous message: Brian Bushay TeamB: "Re: ADOtable Excel"
- Next in thread: Jim Albertson: "Re: "Field cannot be updated" error with ADODataSet"
- Reply: Jim Albertson: "Re: "Field cannot be updated" error with ADODataSet"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]