Rafal Krzewski wrote:
> Are you really sure that your table has a proper entry
> in the ID_TABLE? For me, it looks like the select statement
> in the ID Broker returned 0 rows, but the code tried to
> read values which caused the exception to be thrown.
I've just commited a patch that makes ID Broker throw
an exception with meaningfull message when the above
situation occurs.
Rafal
--
Rafal Krzewski
Senior Internet Developer
mailto:[EMAIL PROTECTED]
+48 22 8534830 http://e-point.pl
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
