[AccessD] VBA Unbound data entry / update form

Rocky Smolin at Beach Access Software rockysmolin at bchacc.com
Thu May 29 10:48:53 CDT 2008


This is a debate about religion.  Move it to OT please.
 


Rocky Smolin
Beach Access Software
858-259-4334
www.e-z-mrp.com
www.bchacc.com
 
 

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

Drew, c'mon.

The ONLY direct answers to my questions about how to design an unbound form
came from Rocky (thanks Rocky!).  There was a suggestion (also not from you)
about how to handle the locking for an unbound edit.  Gustav came up with a
rather nice idea of just disconnecting the memo field itself and leaving the
rest bound.

The rest were answers to a question I didn't ask, which is how YOU think the
system needs to be redesigned.

Now you want to pick a fight because I am not interested in redesigning the
system.  Sorry, but I am not.  I am interested in a simple means of yanking
the memo field out into an unbound control, editing it and placing it back.

I got the answer to that, but it was NOT from you.  Read your posts and copy
and paste any of your responses that answered my question if you so wish
(but NOT your answers to any questions I did not ask).  Sorry, but I don't
have them available because I trash responses that are useless to me.

All of your blathering isn't helping me so it is going in the trash.
Including this one.

John W. Colby
www.ColbyConsulting.com


Drew Wutka wrote:
> LOL.  I doubt there will be a fight here.  He asked how to make 
> something unbound.  He was told.  He whined and complained and said 
> that he didn't understand why bad table design would affect an
application.
> I normally don't get involved in a battle of wits with an unarmed man...
> ;)
> 
> Drew
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte 
> Foust
> Sent: Thursday, May 29, 2008 9:53 AM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] VBA Unbound data entry / update form
> 
> Ooooh, here it comes! 
> 
> Getcha peanuts, popcorn, crackerjack!!  Can't enjoy the fight without 
> peanuts!  Peanuts, Mister?
> 
> Charlotte
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Drew Wutka
> Sent: Thursday, May 29, 2008 7:49 AM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] VBA Unbound data entry / update form
> 
> Ugh, I explained exactly what you need to do to do it unbound.  It 
> would run circles around what you currently have in place.
> 
> You went...whaaa whaa whaa, my customer doesn't want it done right, I 
> am a slave to my customers unreasonable demands.
> 
> And instead of listening, and realizing that you could do what you 
> customer really wanted (and far more), you had this stupid idea stuck 
> in your head that an unbound form was just a form, and not a complete 
> structure instead.  If you want to build an interface over a crappy 
> table structure, bound is certainly the way to go.  Good luck with 
> that....
> 
> Drew
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
> Sent: Thursday, May 29, 2008 7: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
> 
> 
> 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.
> 
> 
> --
> 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

No virus found in this incoming message.
Checked by AVG. 
Version: 8.0.100 / Virus Database: 269.24.3/1472 - Release Date: 29/5/2008
07:27




More information about the AccessD mailing list