In this case I suppose that the exception is caused by an attempt to access the database field "key.newkey", which for some reason, doesn't exist.
Have you tried the above query in a SQL prompt? What does it return? 2007/4/6, Ian Piper <[EMAIL PROTECTED]>: > I have a fairly simple piece of code that is creating an exception, > and I can't understand why. This code checks a database table for the > existence of a record with a particular field populated. The first > time the table has no rows, so I am expecting temp to be "" in the > example below on the first run, (because rs.RecordCount > 0 should be > false). So I can't understand why the code is stepping into that if > statement nor indeed why it then raises an exception. -- Best regards, Bastian Bense _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
