Le vendredi 15 juillet 2005 à 16:04 +0100, Phill Gillespie a écrit : Hi Phill,
> The simple work around is to remove Unsigned from all these fields > (ironically I only added Unsigned to them as in an early 1.1 release the > tick boxes were setting the field to be either -1 or 0 which would give > blank or a grey-ed out tick). Unfortunately, a work-around of that type would mean I'd have to redefine all of my MySQL tables, something I'm not prepared to do. This isn't the first time I've had problems with unsigned fields and OOo 2, in an earlier version I had set the field to int(3) unsigned, and OOo simply kept putting in the max value for a signed field of 3, i.e. 127, for any value that I entered that was above 127 - most frustrating, especially when it was an autoincrement field. Alex --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
