Bruce H. Johnson
bhjohnson at verizon.net
Sat Jun 10 16:44:08 CDT 2006
I used to do disconnected records way back in Dbase II and IV. It was a read the record (make it current) then fill the display with the fields. On the update, I could do all the cross-checks, validation, etc. much easier than with a bound record. With modern field binding, edit masks, etc. it's a lot easier than it was. Now that was something like 30 years ago. Even nowadays, when I look at displaying/editing/updating recordsets I take into account the underlying database system and decide if unbound records might be the way to go. Sometimes it is, sometimes it isn't. I guess the main point is that we have a choice. Bruce H. Johnson Sylmar, CA -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence Sent: Saturday, June 10, 2006 2:24 PM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] A2000: Move to next record - Not Bound Hi Darren: ----- snipped ----- 1. Create a recordset list (disconnected) which contains just display information (i.e. name and/or product) and the key. 2. Create a recordset which purpose is to hold the contents of a specific/current record or set. 3. As the user moved from one record to the next the list recordset refreshes the current key from the present record. 4. The key parameter is sent to server which in turn supplies all the fields required repopulating the current record set and that information refills the record display. At this time you can attempt to lock the current record... by using a connected recordset and applying the appropriate locks but depending on the data source there are a number of techniques to manage that. It may seem like a long way around but it is very fast and flexible. You can hook in virtually any data source(s) simultaneously. HTH Jim -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Darren DICK Sent: Friday, June 09, 2006 6:17 AM To: 'Access Developers discussion and problem solving' Subject: [AccessD] A2000: Move to next record - Not Bound Hi all I am going to try an unbound experiment (I know I know) - all the Unbounders - back in yer seats So...What's the syntax for not binding a form to a table or query I assume you find the first record in the table you want to display and bind the form to one record at a time? (So it's not true unbound - I agree but...) How do you move to the next or previous records? Using something like... select * from Accounts where AccountID = me.txtAccountID + 1 won't successfully navigate me forward or back - I need to 'ignore' deleted records etc So what's the general consensus for navigating forward and back through single records at a time? many thanks in advance Darren -- 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