[AccessD] VBA Unbound data entry / update form

Yes, I did, you just ignored it.

However, I just posted an example. It was built for one user to use.
Though to make it multi user wouldn't have been very difficult.  It
would simply require a little extra to 'alert' other open instances to
updates (using TCP/IP broadcasts, pretty simple, but wasn't needed when
that application was built).

Drew

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
Sent: Tuesday, June 10, 2008 12:00 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] VBA Unbound data entry / update form

LOL, OK.  The devil is in the details after all.

I am not really interested in locking.  In my understanding of unbound
forms, you don't hold locks, and if you are, you might as well go bound.

Which leads us squarely back to update strategies, and testing for
modifications by other users.  All that good stuff that the "unbounders"
claim to handle but have never piped up with even general strategies,
never mind code.

John W. Colby
www.ColbyConsulting.com


Rocky Smolin at Beach Access Software wrote:
> Not ignoring.  It wasn't an exhaustive treatise on the subject.  Just 
> a 'how to get started'.  Locking:  you have to look up record and page

> locking stuff for DAO.
> 
> 
> Rocky Smolin
> Beach Access Software
> 858-259-4334
> www.e-z-mrp.com
> www.bchacc.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.