Max Wanadoo
max.wanadoo at gmail.com
Thu Jan 1 07:31:25 CST 2009
Rocky, I don't think this error has anything to do with the line of code you are on. It is just that this is where it appears when the engine is processing the request. I get this from time to time and I think that it is related to exactly what it says, ie. The index for the table has become corrupt. I don't even bother now to figure it out. When it happens, I get everybody off the mdb FE and then go to the BE and repair/compile. This always cures it. I don't do anything to the FE. When next used it works ok. HTH Max -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin at Beach Access Software Sent: 31 December 2008 22:15 To: 'Access Developers discussion and problem solving' Subject: [AccessD] Error 3709 The search key was not found in any record Dear List: I'm getting an error in A2007 which does not occur in A2003. It is Error 3709: The search key was not found in any record. It happens in a line of code reading Me.OrderBy = strSort, where strSort contains the fields by which to sort the recordset. I found one reference to this on the web which said it was due to a corrupted record but since it works in 2003 and not 2007 I don't think that's it. In any event I went through the make table solution but no luck. Has anyone seen this before and have a solution or an insight into the problem? MTIA Rocky Smolin Beach Access Software 858-259-4334 www.e-z-mrp.com <http://www.e-z-mrp.com/> www.bchacc.com <http://www.bchacc.com/> -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com