[AccessD] VBA Unbound data entry / update form

Drew Wutka DWUTKA at Marlow.com
Wed May 28 17:29:54 CDT 2008


Apparently you didn't read any of the 47 other posts. ;)

The separate table for memos allows you to create a memo for each entry,
with an foreign key linking the memo to the record.  And with the memo
being 'unbound' (meaning it is read in a flash, and cached, thus only
locked for the split second, and when saved, is just a new added memo
field in a new record, again, only locking it for a split second), you
get no error locks!  It's a one to many situation, and all your problems
disappear...which is what I said from the get go about the table design,
which you said the customer doesn't want to change.......but fixes the
problem in a heartbeat!

Drew

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
Sent: Wednesday, May 28, 2008 4:46 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] VBA Unbound data entry / update form

LOL.

You know what, I may yet use a piece of that.  I am not sure 
if the "separate table" is useful or not.  I would be 
interested in hearing how you came to use that construct. 
The "partially bound" with the memo itself unbound is a 
brilliant idea.  Kinda "the best of both worlds".  the 
record lock does not take effect because of an edit to the 
memo (which is the only field edited the second and 
subsequent times) and the locked flag would solve the rest.

So why the separate table for memos?

John W. Colby
www.ColbyConsulting.com


The information contained in this transmission is intended only for the person or entity to which it is addressed and may contain II-VI Proprietary and/or II-VI Business Sensitive material. If you are not the intended recipient, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. You are notified that any review, retransmission, copying, disclosure, dissemination, or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited.





More information about the AccessD mailing list