[AccessD] VBA Unbound data entry / update form

jwcolby jwcolby at colbyconsulting.com
Tue May 27 20:29:29 CDT 2008


 > However, where JWC is hitting a wall, is that he is 
trying to mimic the exact functionality of a bound form with 
unbound methods

Well... there is far too much "exact functionality" to even 
attempt to mimic, though the major parts would be nice.

 >though I know why he is, he is trying to disconnect it to 
try and remove a clog in the system

Uhhhh yep.  Under certain conditions Jet and the MDB BE 
cause issues.  I am trying to code a solution around those 
issues, not for use in every form, but I still need add / 
edit / delete functionality without data corruption.

 >The problem is that if you want all the features of a 
bound system, it's FAR easier to just use a bound system. 
Unbound forms are good for lightweight processes.

Which is precisely why I use bound forms 99% of the time. 
Why reinvent a rather complex, well designed wheel.  Said 
wheel works quite well BTW with a SQL Server data store, it 
is SPECIFIC issues with the MDB data store that appear to be 
the problem.

John W. Colby
www.ColbyConsulting.com


Drew Wutka wrote:
> Sorry, just don't build Access front ends very often.  ASP/HTML has far
> too many advantages.
> 
> However, where JWC is hitting a wall, is that he is trying to mimic the
> exact functionality of a bound form with unbound methods....there's no
> real point to do that. (though I know why he is, he is trying to
> disconnect it to try and remove a clog in the system).  The problem is
> that if you want all the features of a bound system, it's FAR easier to
> just use a bound system. Unbound forms are good for lightweight
> processes.
> 
> Look at it this way.  A bound form is essentially like giving someone
> direct access to a table, with some extra bells and whistles.  To
> restrict capabilities (like not allowing certain fields to be edited, or
> only certain records, etc.) you have to add to a bound form to get those
> capabilities.  With an unbound form, you are coming from the opposite
> direction.  The user only gets the capabilities you create for them.  
> 
> Drew
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jennifer
> Gross
> Sent: Tuesday, May 27, 2008 7:12 PM
> To: 'Access Developers discussion and problem solving'
> Subject: Re: [AccessD] VBA Unbound data entry / update form
> 
> I have no idea how to create an unbound form in Access.  I always use
> bound
> forms.  Though I would be interested to know how it's done.  Unless I've
> got
> it wrong, that seems to be the basic question here - For those of you
> who do
> it, how do you create an unbound form?  How do you populate the
> textboxes
> initially and then how do you save the information back to the tables?
> 
> It's beginning to sound like nobody really does it.
> 
> Jennifer
> 
> 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