Crashes on the first call to rs.next()....
Exception in thread "main" java.lang.ArrayIndexOutOfBoundsException: 2048
at com.hxtt.sql.access.t.a(Unknown Source)
at com.hxtt.sql.access.t.a(Unknown Source)
at com.hxtt.sql.access.r.a(Unknown Source)
at com.hxtt.sql.access.r.a(Unknown Source)
at com.hxtt.sql.access.u.a(Unknown Source)
at com.hxtt.sql.l.a(Unknown Source)
at com.hxtt.sql.q.a(Unknown Source)
at com.hxtt.sql.q.a(Unknown Source)
at com.hxtt.sql.bi.n(Unknown Source)
at com.hxtt.sql.cm.a(Unknown Source)
at com.hxtt.sql.cm.a(Unknown Source)
at com.hxtt.sql.b8.a(Unknown Source)
at com.hxtt.sql.b8.next(Unknown Source)
at org.hibernate.loader.Loader.doQuery(Loader.java:685)
at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:224)
at org.hibernate.loader.Loader.doList(Loader.java:2150)
at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2029)
at org.hibernate.loader.Loader.list(Loader.java:2024)
at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:369)
at org.hibernate.hql.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:300)
at org.hibernate.engine.query.HQLQueryPlan.performList(HQLQueryPlan.java:153)
at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1127)
at org.hibernate.impl.QueryImpl.list(QueryImpl.java:79)
at com.medicaltelecom.mailing.bridge.DocDBGeneric.getServices(DocDBGeneric.java:26)
at com.medicaltelecom.mailing.command.BridgeDoctorDBCommand.execute(BridgeDoctorDBCommand.java:183)
at com.medicaltelecom.mailing.bridge.BridgeDoctor.main(BridgeDoctor.java:354)
Using SQL
select medtelserv0_.UniqueID as UniqueID2_, medtelserv0_.Date as Date2_, medtelserv0_.DiagCode as DiagCode2_, medtelserv0_.ProcedureCode as Procedur4_2_, medtelserv0_.BillID as BillID2_
from Procedure medtelserv0_ where medtelserv0_.Date>?
|
It seems that HXTT Access met an unexpected data in your database. You can zip and email us a sample mdb, then we will dig out and support it in 24 hours.
|
Thanks for the quick reply.
Unfortunately, the data is confidential and I cannot send the DB. After I ran the compress and repair function in Ms Access the problem disappeared...
Cheers,
Martin
|
According to one similar MS Access 2000 sample from another user, that unexpected data has been supported since April 26th, 2006.
|