SPAM-LOW: RE: [AccessD] Capturing the Drop Changes/Copy to Clipboard errormessage?

Christopher Hawkins clh at christopherhawkins.com
Thu Jul 7 18:17:19 CDT 2005


Yes, I know about Edited Record.  The problem is that the creator didn't use it when the app was originally built,  and due to the way this kludgey thing has evolved over the years, changing it to Edited Record now causes errors.

Hence my need for a way to hook into that error.

Surely someone at some point must have done this?

-C-

----------------------------------------
 From: "Dan Waters" <dwaters at usinternet.com>
Sent: Thursday, July 07, 2005 2:52 PM
To: "'Access Developers discussion and problem solving'" <accessd at databaseadvisors.com>
Subject: SPAM-LOW: RE: [AccessD] Capturing the Drop Changes/Copy to Clipboard errormessage? 

Christopher,

If you set the database to Edited Record, then users can't step on each
other's toes. When one user begins to edit a record, all others are
prevented from beginning to make any changes until the first user's changes
are saved to the table.

HTH,
Dan Waters

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Christopher
Hawkins
Sent: Thursday, July 07, 2005 3:18 PM
To: accessd at databaseadvisors.com
Subject: [AccessD] Capturing the Drop Changes/Copy to Clipboard
errormessage?

We may have discussed this in years past, I don't recall.

A client with a mission-critical but shoddily-written Access app ( a
situation we're all far, far too familiar with) is having a problem with
users stepping on one another's changes and getting that error message that
says:

"This record has been changed by another user since you started editing it.
If you save the record, you will overwrite the changes the other user made.

Copying the changes to the clipboard will let you look at the values the
other user entered, and then paste your changes back in if you decide to
make the changes. "

There's GOT to be a way to capture this message and either handle the
conflict programmatically, or swap out a friendlier message, or both.  Even
if it involves hooking into an API somewhere, there's GOT to be a way.

Has anyone done it, or know someone who has, or know where to find pointers
on how to do it, or anything?

-C-

--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com





More information about the AccessD mailing list