ADE Write Conflicts

  • Thread starter Thread starter Jeff via AccessMonster.com
  • Start date Start date
J

Jeff via AccessMonster.com

Just wondering if there's a way of avoiding the write conflict message when
multiple users try editing the same record.
 
The simplest way: redesign your database to split the record into smaller
(and probably more logical) datums.

Two other possibilities are to use unbound forms and make the update
yourself or try to use views created with the VIEW_METADATA option and an
INSTEADOF trigger. (However, I never tested the last one with ADP).
 
Hello Jeff:
You wrote in conference microsoft.public.access.adp.sqlserver on Fri, 20
May 2005 13:03:29 GMT:

JvA> Just wondering if there's a way of avoiding the write conflict message
JvA> when multiple users try editing the same record.

In my project, when user A is opening an order which is being worked with by
user B, A receives a warning: "B is working with this record and can
overwrite your changes; B's phone # is xxx." (phone number taken from AD).
This is done by UDP broadcasting on record opening.

Also, whenever someone is blocked by someone else, both receive net send messages:
"you are blocking user X with your application Y. Please complete your
operation if you can", "You are blocked by user Z, whose phone is ZZ. ".
This is done on the server level.


Vadim
 
Vadim,

I'm not familiar with UDP Broadcasting. Can you give me a bit more
information? I'm particularly interested in:

"In my project, when user A is opening an order which is being worked with
by user B, A receives a warning: "B is working with this record and can
overwrite your changes; B's phone # is xxx." (phone number taken from AD).
This is done by UDP broadcasting on record opening."

Thanks,
 
Hello Jeff:
You wrote in conference microsoft.public.access.adp.sqlserver on Tue, 24
May 2005 13:31:45 GMT:


JvA> I'm not familiar with UDP Broadcasting. Can you give me a bit more
JvA> information? I'm particularly interested in:

JvA> "In my project, when user A is opening an order which is being worked
JvA> with by user B, A receives a warning: "B is working with this record
and can
JvA> overwrite your changes; B's phone # is xxx." (phone number taken from
JvA> AD). This is done by UDP broadcasting on record opening."


if you have vb6, then you have winsock component. Create a sample project in
vb6 with it to see how it works. VB6 Online Help has a sample code, it's
very simple. Then, in ADP (with winsock control on the form, when UserA
opens the order, his ADP broadcasts "I'm opening order x". Others' ADP's
hear it and compare to the orders they are working with; whoever has the
match, broadcasts "I'm already working with order X; I'm UserB, my phone
xxx". UserB receives it and shows a message "John is already working with
this order, his phone xxx".

Perfect solution would also have 3rd message: in case UserA has decided to
go ahead, UserB should receive a warning about it: "you're not alone now".


Vadim
 
I take it I'll need the Developer's version of Access in order to use the
WinSock controls. Is there another way around this?
 
Hello Jeff,
You wrote in conference microsoft.public.access.adp.sqlserver on Thu, 26
May 2005 16:50:14 GMT:

JvA> I take it I'll need the Developer's version of Access in order to use
JvA> the WinSock controls.

I doubt it. That control is from VB6. I don't recall it included in Office
Developer.


Vadim
 
Back
Top