[AccessD] VBA Unbound data entry / update form

LOL, in fact I would have the same problem if the table was 
properly normalized.  The real issue is too many people 
using a bound form form in an MDB database BE to edit Memo 
fields which cause page lock issues.

My problem is simply that in this kind of situation, an 
unbound solution is likely superior, and I have no 
experience implementing that!

I think Max's lock field concept is probably as good an 
answer as any, and maybe the best answer in this specific 
instance.

I am leaving the floor open for other ideas, now that the 
real issue is under discussion.

John W. Colby
www.ColbyConsulting.com


Jennifer Gross wrote:
> Can't help you with the unbound forms John since I don't use them in the way
> you need.  But I completely sympathize with having a problem to solve where,
> if you had it your way the problem wouldn't exist in the first place.
> 
> Jennifer 
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
> Sent: Wednesday, May 28, 2008 11:28 AM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] VBA Unbound data entry / update form
> 
> Uhh... Yep.  I do all of my work by the hour.
> 
> I am very good at what I do, and I always advise the client of the "right
> way" to do things.  Mostly they just let me do it the way I think it should
> be done,  and occasionally they don't.  Usually when they don't there is a
> reason, which I listen to and see if we can "do it right" and still have
> what they really need.  Very occasionally, I just end up doing it the way
> they demand.
> 
> I have been trying very hard not to get up in arms about this thread but it
> was just getting out of hand.  I need useful ideas, not "that is just bad
> design".  I am treading in an area that I am not fluent in (unbound data
> entry
> forms) and what I need is not what I am getting (mostly).
> 
> John W. Colby
> www.ColbyConsulting.com