[AccessD] VBA Unbound data entry / update form

Jennifer Gross jengross at gte.net
Thu May 29 11:52:15 CDT 2008


>>What I want to know more than anything else is how does Access discover
the lock on a record in order to display the lock symbol in the selector bar
on the left.  And why did they not expose that to us?

This was exactly my question a week or so ago . . . and who the heck is
locking the record . . . how do they know that and why isn't it exposed!?

Jennifer 

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

Gustav,

Maybe... all the UHU members, being coders at heart, have left us for other
platforms, leaving only bounders in our midst?

;-)

And yes, I am attempting to be charitable here.

8-)

 > I have in a few cases used unbound forms (small and no
subforms) and was surprised to find out how many tasks you needed to take of
- your initially simple code quickly bloats to a mess.

I would think so.  What I want to know more than anything else is how does
Access discover the lock on a record in order to display the lock symbol in
the selector bar on the left.  And why did they not expose that to us?

John W. Colby
www.ColbyConsulting.com


Gustav Brock wrote:
> Hi John
> 
> Yes, I'm a bit surprised too and did expect - of curiosity only - to see
at least one solid implementation even though it might have been a clean VB6
solution.
> 
> I have in a few cases used unbound forms (small and no subforms) and was
surprised to find out how many tasks you needed to take of - your initially
simple code quickly bloats to a mess.
> 
> /gustav
> 
>>>> jwcolby at colbyconsulting.com 29-05-2008 13:19 >>>
> Gustav,
> 
> There is another saying... all other things being equal, simpler is 
> always better.  Your solution is an hour to implement.  The Gift Horse 
> is not.
> 
> I am not looking for a Ferrari, I am looking to fix one single lonely 
> little problem with my VW.  Your solution and a lock field certainly 
> appears to do so.
> 
> And yes, How much "unbound is soooo much better" crap did I endure 
> during the great bound / unbound debate.  Given all of that I expected 
> a host of angels to descend on me telling me all of the cool and 
> wonderful things that you could do unbound and how you would go about 
> it.
> 
> Seems strangely quiet, don't you agree?  Tons of "bad design", 
> virtually no "here's how to do unbound".
> 
> John W. Colby
> www.ColbyConsulting.com
> 
> 
> Gustav Brock wrote:
>> Hi William
>>
>> You are a man of great humour. As a foreigner I had to look this up:
>>
>>   http://www.goenglish.com/DontLookAGiftHorseInTheMouth.asp
>>
>> Makes perfectly sense. 
>>
>> However, have you ever had a gift which you expected to be something
quite different? It may cause great disappointment. So let us forgive JC; he
was wishing for the superior and sparkling unbound solution - the jacket
from the top store in town he could flash on his bike - but was left with a
ground level mostly bound modification - a military coloured not very sexy
pullover though equipped with a smart zipper.
>>
>> /gustav
>>
>>
>>>>> wdhindman at dejpolsystems.com 29-05-2008 04:46 >>>
>> ...hate to say this JC but I think you're looking a gift horse in the 
>> mouth ...this is almost exactly the way I handle customer contact 
>> records ...it works without any lock conflicts, its much more 
>> flexible and user friendly than a single huge memo field, and indexed 
>> search functions are much faster than text searches ...and the user 
>> can't tell the difference from the single memo field approach except for
speed and lack of problems.
>>
>> ...its your problem of course but it looks like you've gotten locked 
>> into looking at it a certain way and thus dismissing out of hand 
>> solutions that really do address each of your stated issues.
>>
>> William
>>
>> --------------------------------------------------
>> From: "jwcolby" <jwcolby at colbyconsulting.com>
>> Sent: Wednesday, May 28, 2008 9:00 PM
>> To: "Access Developers discussion and problem solving" 
>> <accessd at databaseadvisors.com>
>> Subject: Re: [AccessD] VBA Unbound data entry / update form
>>
>>>> If you REALLY must have a demo for this, let me know,
>>> maybe I can do that tomorrow....
>>>
>>> LOL, no really, not needed.
>>>
>>> John W. Colby
>>> www.ColbyConsulting.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