On Thursday 18 October 2007 01.01:28 Drew Jensen wrote: > Adrian von Bidder wrote: > > Hi! > > > > I have a DB-backed form (sybase over jdbc on Linux), and upgrading from > > oo.org 2.0 to 2.3 (and I later also updated upgrading from jvm 1.5 to > > 1.6 and Sybase jConnect from 5.x to 6.0), the form now suddenly is read > > only. > > > > Anyobdy knows where to look? > > > > Strangely, while I can edit the form data in 2.0 just fine in the form, > > and the updates are really stored to the db, I can't edit the data when > > I open the data source (.odb document, or even just the data source > > view by pressing F4) with oobase. I guess there might be a connection > > there, but I don't work much with oobase myself (the form was designed > > by somebody not working here anymore...) > > > > cheers > > -- vbi > > Hi vbi > > OK - just a thought on this. When you updated from 2.0 .> 2.3 the > settings for java would have remained the same.
Yes, I told oo.org to use the new jvm (what a stupid concept, imho, why not
by default just use what's in /usr/bin/java or $JAVA_HOME?)
dito for jconnect, I used com.sybase.jdbc3 or whatever the new classes are
for jConnect 6.
> most likely you are using an older version driver to connect to a newer
> version database.
So no, that's not the case (and the db version has not changed, btw).
Still, thanks.
Meanwhile, I tried using unixodbc/freetds, which strangely shows exactly the
same behaviour (#63448 on the dba bugtracker say that ODBC should work.)
Will try the Symantec ODBC drivers next.
cheers
-- vbi
--
ocusing on encryption is like sticking a tall stake in the ground and
hoping the enemy runs right into it, instead of building a wide wall.
-- Bruce Schneier
signature.asc
Description: This is a digitally signed message part.
