[AccessD] VBA Unbound data entry / update form

Jim Lawrence accessd at shaw.ca
Tue Jun 10 17:07:08 CDT 2008


They have Liz:

20 years ago there were no tightly bound databases. Bound database are a
relatively new phenomena. With the growth of stand-alone pure databases,
with all their sophisticate conflict management routines and the growth of
web based products tightly-bound applications are going by the board. One
day I am sure bound databases will just be a point of conversation for us
old guys and little more.

In the 10 years of using unbound DBs, I have never been made aware of a
single piece of lost data due to a non binding issue.... In fact quite the
contrary is true, though. 

Jim

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
Elizabeth.J.Doering at wellsfargo.com
Sent: Tuesday, June 10, 2008 10:10 AM
To: accessd at databaseadvisors.com
Subject: Re: [AccessD] VBA Unbound data entry / update form

I suspect that the unbounders on this list have all been converted and
are therefore silent.  :) 


Thanks,   


Liz   



 
 
This message may contain confidential and/or privileged information. If
you are not the addressee or authorized to receive this for the
addressee, you must not use, copy, disclose, or take any action based on
this message or any information herein. If you have received this
message in error, please advise the sender immediately by reply e-mail
and delete this message. Thank you for your cooperation.



-----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
>  
>  
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
> Sent: Tuesday, June 10, 2008 9:07 AM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] VBA Unbound data entry / update form
> 
> Rocky,
> 
> I hate to jump all over your method because I want a method to use, 
> but you are completely ignoring locking / update issues.  What 
> happened if another user updated the record between the time you 
> loaded yours and the time you write it back?
> 
> John W. Colby
> www.ColbyConsulting.com
> 
> 
> Rocky Smolin at Beach Access Software wrote:
>> I know how to make an unbound form but I haven't got enough nerve to 
>> present such heresy - it runs counter to strongly held religious
beliefs.
>>
>> OK - briefly - but you didn't hear it from me.
>>
>> 1. Design your form as you would a bound form but no Control Source 
>> in the text boxes.
>> 2. Create a recordset in the Open event of the form (DAO or ADO - I 
>> prefer
>> DAO) using pretty much the same SQL or query as you would for your 
>> Record Source in a bound form.
>> 3. Add a module to put the fields from the current record of the 
>> recordset into the text boxes which you can call whenever you want to

>> display the data on your form.
>> 4. Add a module to put the values in the text boxes into the fields 
>> of the current record (in DAO use .Edit or .Add and .Update) which 
>> you can call whenever you want to write the textbox values back to
the table.
>> 5. I always put my own navigation buttons on the unbound for - First,

>> Last, Next, Previous with Click events that move the recordset point 
>> appropriately.
>>
>> HTH
>>
>> 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 Jim 
>> Lawrence
>> Sent: Monday, June 09, 2008 5:38 PM
>> To: 'Access Developers discussion and problem solving'
>> Subject: Re: [AccessD] VBA Unbound data entry / update form
>>
>> Hi Jennifer:
>>
>> I have no idea how to create bound Access forms. ;-) The last bound 
>> database that I have worked with was back in '97.
>>
>> Jim
>>
>> -----Original Message-----
>> From: accessd-bounces at databaseadvisors.com
>> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jennifer 
>> Gross
>> Sent: Tuesday, May 27, 2008 5: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
--
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




More information about the AccessD mailing list