mystery table name

[Kim Goings]

As this is my first post, let me say that I think iBatis is FANTASTIC!  Now, on to business.  

I'm getting an exception back from an update statement which indicates that the SQL contains an invalid table name, yet the debug output from iBatis shows a different (correct) table name in the statement.  It seems the exception doesn't match up with what should be going over the wire.  Could there be some kind of caching going on with the statements somewhere?  I don't doubt that I had the name misspelled at some point.  Can anyone provide any more insight on where I should look?  I've been chasing this for a while, so it may be something obvious I'm just not seeing.  Trace below.


<x-tad-bigger>|aef|09:43:00.033|DEBUG|{pstm-100078} PreparedStatement:     UPDATE FREQUENT_MEMBER_CLUB     SET ATTENDEE_ID = ?,      TYPE = ?,      COMPANY = ?,      MEMBER_ID = ?,      MODIFIED_BY = ?     WHERE ID = ?    [http-8080-Processor25|java.sql.PreparedStatement]</x-tad-bigger><x-tad-bigger>
</x-tad-bigger><x-tad-bigger>|aef|09:43:00.041|DEBUG|{pstm-100078} Parameters: [2, 0, fdasfd, ffdsafa, user, 3] [http-8080-Processor25|java.sql.PreparedStatement]</x-tad-bigger><x-tad-bigger>
</x-tad-bigger><x-tad-bigger>|aef|09:43:00.063|DEBUG|{pstm-100078} Types: [java.lang.Integer, java.lang.Integer, java.lang.String, java.lang.String, java.lang.String, java.lang.Integer] [http-8080-Processor25|java.sql.PreparedStatement]</x-tad-bigger><x-tad-bigger>
</x-tad-bigger><x-tad-bigger>|aef|09:43:53.471|ERROR|<?xml version="1.0" encoding="UTF-8"?></x-tad-bigger><x-tad-bigger>
</x-tad-bigger><x-tad-bigger><message>Could not save travel profile: [EMAIL PROTECTED]</message><throwable>com.ibatis.common.jdbc.exception.NestedSQLException:   </x-tad-bigger><x-tad-bigger>
</x-tad-bigger><x-tad-bigger>--- The error occurred in config/FrequentMemberClub.xml.  </x-tad-bigger><x-tad-bigger>
</x-tad-bigger><x-tad-bigger>--- The error occurred while applying a parameter map.  </x-tad-bigger><x-tad-bigger>
</x-tad-bigger><x-tad-bigger>--- Check the com.levelfivesolutions.eventmgr.dao.AttendeeFrequentMemberClub.update-InlineParameterMap.  </x-tad-bigger><x-tad-bigger>
</x-tad-bigger><x-tad-bigger>--- Check the statement (update failed).  </x-tad-bigger><x-tad-bigger>
</x-tad-bigger><x-tad-bigger>--- Cause: java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Invalid object name 'FREQUENCT_MEMBER_CLUB'.</x-tad-bigger><x-tad-bigger>
</x-tad-bigger><x-tad-bigger>Caused by: java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Invalid object name 'FREQUENCT_MEMBER_CLUB'.</x-tad-bigger><x-tad-bigger>
</x-tad-bigger><x-tad-bigger>	at com.ibatis.sqlmap.engine.mapping.statement.GeneralStatement.executeUpdate(GeneralStatement.java:87)</x-tad-bigger><x-tad-bigger>
</x-tad-bigger><x-tad-bigger>	at com.ibatis.sqlmap.engine.impl.SqlMapExecutorDelegate.update(SqlMapExecutorDelegate.java:500)</x-tad-bigger><x-tad-bigger>
</x-tad-bigger><x-tad-bigger>	at com.ibatis.sqlmap.engine.impl.SqlMapSessionImpl.update(SqlMapSessionImpl.java:89)</x-tad-bigger><x-tad-bigger>
</x-tad-bigger><x-tad-bigger>	at com.ibatis.sqlmap.engine.impl.SqlMapClientImpl.update(SqlMapClientImpl.java:61)</x-tad-bigger><x-tad-bigger>
</x-tad-bigger><snip/>  


Thanks,
Kim