jwcolby
jwcolby at colbyconsulting.com
Tue Jun 10 11:59:37 CDT 2008
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