WITPSTAFF

[michelzzt]

Hello ;
I don't why by now I am unable to initialize a newdata base with witpstff. Every time this message appears :


Could not create or initialize the database

java.sql.SQLException:Wrong data type:
java.lang.illegalArgumentException in statement[CREATE MEMORY]
TABLE"Turn2Date" ("date"DATE default'0000-00-00')

Thank you for help.

I encounter the same difficulties with windows XP or W7 64bits, my game version is 1.04.1106g

[n01487477]

ORIGINAL: michelzzt

Hello ;
I don't why by now I am unable to initialize a newdata base with witpstff. Every time this message appears :


Could not create or initialize the database

java.sql.SQLException:Wrong data type:
java.lang.illegalArgumentException in statement[CREATE MEMORY]
TABLE"Turn2Date" ("date"DATE default'0000-00-00')

Thank you for help.

I encounter the same difficulties with windows XP or W7 64bits, my game version is 1.04.1106g

Witpstaff has not been updated in some time. I think it lost functionality some time ago with an AE and Javapatch that caused the DB to not initialise properly. I'll stand corrected if this is not the case.
See these messages in this thread for more ...
fb.asp?m=2363701
fb.asp?m=2377518

The replacement is WitpTracker which you will find a link to in the Sticky section of the main forum.

[michaelm75au]

It sounds a bit like the Java Update 18 that affect how date was interpreted.
 

[n01487477]

ORIGINAL: michaelm
It sounds a bit like the Java Update 18 that affect how date was interpreted.

Yeah Micheal,
that's why I posted the links; I believe that if you use Java update 17 it may work ... but I thought an AE patch also rendered Staff to the Unemployment lines ... (pun intended) [;)]

[michaelm75au]

ORIGINAL: n01487477

ORIGINAL: michaelm
It sounds a bit like the Java Update 18 that affect how date was interpreted.

Yeah Micheal,
that's why I posted the links; I believe that if you use Java update 17 it may work ... but I thought an AE patch also rendered Staff to the Unemployment lines ... (pun intended) [;)]

Opps. didn't notice it was witpstaff. Just saw the Java reference.
I thought that it was still running under the current AE version. The Xmas patch I think caused some issue that was the last thing that was fixed in witpstaff.

[michelzzt]

Thank you for your posts, I will try to find java update 17.
My previous save with witpstaff are still working.

I use also Witptracker but I like the ship4history included in witpstaff.

[Local Yokel]

I like to use both Staff AND Tracker, and wasn't aware of a problem with Staff until I saw this thread.

I'm running Windows XP on a fairly ancient machine, Witp AE version 1.0.4.1106g. According to the Java Control Panel, my Java version is 6 Update 18, but I don't entirely trust that information, as I see I downloaded Update 17 some time ago, possibly to address the very problem encountered here. OTOH the Registry data for the Java Runtime does confirm that my current version is 1.6.0_18. If I did overwrite Update 18 with Update 17, then it hasn't altered the Registry's information about which version of Java I am running. And I see Java can now be updated to Update 22!

I ran a test of initialising a new Staff database for a PBEM Scenario 1 game, playing Japanese side. The database initialised correctly and I was able to load the first game turn's save file and view its data through Staff without error.

I'm therefore not sure whether there really is an incompatibility between Staff and the version of Java the OP is using. But I see no signs of changes to the game itself having led to such an incompatibility, as I think I am running the most up-to-date version of the game.

If you want to get an old version of the Java runtime, suggest http://www.oracle.com/technetwork/java/archive-139210.html is the place to go. There you can chose the version you want from the JDK/JRE - 6 dropdown list.

[n01487477]

Thanks L.Y,
I thought there was a problem initialising new games with staff because that problem with Java 18 was reported in the Staff thread some time ago... Glad to hear Staff is still working and initialising properly.

Should have tested before I posted