Dan Waters
df.waters at comcast.net
Mon Nov 5 16:29:59 CST 2012
Steve, Take a look at vbWatchdog at www.everythingaccess.com. Using their classes, you can record and later obtain all errors that occur, without adding an error handler to every procedure in your code. It does cost, but it's allowed me to really understand almost all of the Access errors that occur in my systems. When you're using an MDE, you MUST have error trapping of some kind, since the system just crashes without it. And with the error below, you really need to know what triggered that! Dan -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Steve Schapel Sent: Monday, November 05, 2012 4:20 PM To: Access Developers discussion and problem solving Subject: [AccessD] The case of the gutless queries I have just come across a weird one! Easy to fix � I just have to replace the frontend file. But can think of no explanation. Anyone ever seen anything like this?... Access 2003 MDE, with mdb backend on network server. Got a call from the client to say that he was entering data, when suddenly it stopped working. No error apparently. On investigation, this is what I found.... All the queries were empty! I mean blank � not talking data here, I am talking design view of queries with nothing there, and SQL view saying only "SELECT;" All of them ... ppfffft! Just for interest, any thoughts? Regards Steve -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com