Charlotte Foust
cfoust at infostatsystems.com
Fri Jun 9 10:38:12 CDT 2006
No, the simplest way (ignoring those useful and clever classes that some of us adore) is to hold a recordset containing all the records in memory. You don't bind the controls at all, you have code to populate each control when you move forward or back in the recordset. The details differ depending on whether you're using DAO or ADO, but that is the general idea. I have a NoTables sample database you can download that uses an unbound form for data entry and edit if you want to take a look. http://www.rogersaccesslibrary.com/OtherLibraries.asp#Foust,%20Charlotte Charlotte Foust -----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