Re: MySQL Troubles & OOo Base - Solved UNSIGNED

Alex Thurgood wrote:
> 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.
>   

It seems I was actually using an earlier verison of MyODBC (version 2, 
rather than 3.50).  There are no issues with release 3.50 and unsigned 
columns :-)

Unfortunately, under Linux, MyODBC 3.50 makes your data sources appear 
as DatabaseName.TableName rather than just TableName (as version 2 
did).  I've tried asking for advice on the MySQL mailing lists but no 
luck.  Ocke's idea of using the "no catalog" option doesn't work as that 
is only under the Windows setup GUI.  Does anyone here know how to get 
it to revert to the original behaviour?

P h i l l