On Sat, Aug 12, 2006 at 06:48:11PM -0600, Richard Greenwood wrote: > Sounds very much like character encoding, a subject that I am no > expert in. I am using 'UTF8' encoding and it should be of database > scope (not table). I am running postgres 8.1 right now, but I know I > sucessfully connected back in 7.x days, and possibly even eariler.
I tried rebuilding the databse with LATIN1 encoding and then I rebuilt the entire cluster with that encoding, but that text field is still uneditable and in the table structure it's listed with twice the length that it really is. So I went back to the default UNICODE settings and reloaded the database. This is strange because I can modify this field with no problems if I use a FILEDSN and MapBasic, and I can also import it into MS Access and everything is editable. So I looked at the tab file and discovered that the 'name' field was marked as 'readonly'. Just to see what would happen, I removed that, opened the table and modified a few rows. It worked perfectly and updated the remote PostgreSQL table as it should have. So if there's an encoding problem, it doesn't appear to be much of a problem, but I am still curious why when MapInfo opens this table via ODBC, it made this varchar(30) column readonly and thinks it's 60 characters wide, especially in light of the fact that if you remove the readonly flag, it doesn't cause any problems. In any case, I'll only be accessing data via MapBasic and MS Access VBA. Those methods seem to have no porblems, so as far as I'm concerned the interactive method can go hang. But if anyone knows why varchar(n) fields in PostgreSQL get marked as readonly when MapInfo links to them via ODBC, I'd still like to know. - Bill Thoen _______________________________________________ MapInfo-L mailing list [email protected] http://www.directionsmag.com/mailman/listinfo/mapinfo-l
