ConsultComm Project Timekeeper

This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).

Was able to get this working with Java 6 (with MySQL). Any updates?

Could you post or e-mail your URL & driver name?

I extracted all the JAR files from Microsoft and put them together into a
single new jar file.

Now when I use the new jar file and test the connection I get the password
prompt, but an error message saying: "Database Connection Error", "One or
more arguments are null."

C:\Program Files\ConsultComm>"c:\Program Files\Java\jdk1.6.0_01\bin"\java
-Djava
.library.path=syslibs -jar CsltComm.jar
ConsultComm CVS Release, Copyright (C) 2004 John Ellis
ConsultComm comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it under
certain conditions. For details go to Help(F1)->License or view
the COPYING file included with this distribution

Deserializing plugin JDBCConnect from JDBCConnect.xml
Instantiating plugin SysTray from SysTray.jar
Deserializing plugin TimeOut from TimeOut.xml
Error loading file libtimeout.so: java.io.IOException: Stream closed
Deserializing plugin TotalTimes from TotalTimes.xml
Row index invalid, not setting selection.

The last line can repeat when making several test connections.

Most errors are caught and the root cause is displayed to the user. In
this instance, however, there seems to be an issue with your classpath.

I'd recommend re-adding the appropriate JDBC .jar file in the plugin, then
re-typing the corresponding driver name in the dialog box. It appears that
the newest JDBC driver from Microsoft now uses a different driver name -
from the docs it looks like com.microsoft.jdbc.sqlserver.SQLServerDriver

Looks like ConsultComm is getting confused from an older MSSQL JDBC driver
installation and automagically looking for an old driver. By re-adding the
MSSQL JDBC .jar & driver class name you sent a link to you should be okay.

Didn't even think of the command line. :-{
After changing javaw to Java I got a nice exception to work with.
You should catch the exception and report it, instead of letting awt just
swallow it.

The JDBC is Microsoft SQL Server 2000 Driver for JDBC available at
http://www.microsoft.com/downloads/details.aspx?familyid=9f1874b6-f8e1-4bd6-947c-0fc5bf05bf71&displaylang=en


java.lang.NoClassDefFoundError: com/microsoft/jdbc/base/BaseDriver
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(Unknown Source)
at java.security.SecureClassLoader.defineClass(Unknown Source)
at java.net.URLClassLoader.defineClass(Unknown Source)
at java.net.URLClassLoader.access$100(Unknown Source)
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at JDBCConnect.openConnection(Unknown Source)
at FieldMap.setConnection(Unknown Source)
at JDBCConnect.exportTimeRecordSet(Unknown Source)
at JDBCConnect$1.actionPerformed(Unknown Source)
at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
at
javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(Unknow
n Source)
at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown
Source)
at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
at javax.swing.AbstractButton.doClick(Unknown Source)
at javax.swing.plaf.basic.BasicMenuItemUI.doClick(Unknown Source)
at
javax.swing.plaf.basic.BasicMenuItemUI$MouseInputHandler.mouseRelease
d(Unknown Source)
at java.awt.Component.processMouseEvent(Unknown Source)
at java.awt.Component.processEvent(Unknown Source)
at java.awt.Container.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown
Source)
at java.awt.LightweightDispatcher.processMouseEvent(Unknown
Source)
at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Window.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown
Source)

at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown
Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)

I wasn't able to reproduce the problem. What JDBC driver are you using? If
you launch ConsultComm from the command line, do you see any errors when
trying to export to a database?

I haven't tested ConsultComm with Java 6 - just Java 2 (1.4.2 and below).
I'll take a look tonight and hopefully have an updated Database plugin
soon. Not sure what Sun might have deprecated to cause such a problem...
but I'll check.