[Gvsig_english] gvSIG 1.9 (1243) some issues regarding the latest version

[roser]

Hi Wolfgang
I've been testing the problems you repoted and everythig worked fine on 
my computer:
I've been able to make a join with a bew column added to the table,
I've used the joined table to create an event theme
I've exported a table to dbf without problems
I can select more than one item on my linked table that are reflected on 
the other table...
The only thing that gave me problems is the encoding when exporting to 
shapefile the event theme, so I'm reporting this to the developers.
I don't know exactly where is the problem with the other things, I mean, 
I don't know why it works on my computer and not on yours, I'm already 
using bn1244, perhaps it's that.
Sorry I'm not of much help
Thank you for your reports
best regards
Roser


> Dear list,
> some issues I ran into when trying to use gvSIG 1.9 in "real life" 
> regarding tables, join function and event themes.
>
> * JOIN Function:
>    + if a table is loaded into gvSIG and a new column is added (edit 
> mode), gvSIG will not accept this new column within the join dialogue as 
> a key column. It just says: column could not be kept. Workaround: after 
> saving the modified table, the table should be removed from the project 
> manager. Loaded again, the new column is accepted by gvSIG.
> * EVENT theme
>   + it seems to be impossible to use a joined table as an input theme 
> for the event theme dialogue. The strange error message "35" appeared. 
> Workaround for me: export table as xls (dbf does not do the job, see 
> below), open it in openoffice, save as dbf and load that table in gvSIG.
>   + event theme can be created out of the dbf table described above. 
> However, when I export that temporary layer to shapefile, all "umlauts" 
> (ä,ü,ö,ß) will not be displayed correctly. It is not possible to correct 
> this (using extShalom). I just failed. It did not even help to save the 
> original table in utf-8 in open office (utf-8 is the standard encoding) 
> and then create the event theme. EXPORT TO SHAPEFILE WILL ALWAYS RESULT 
> IN BROKEN UMLAUTS. I would be MOST GRATEFUL, if someone would have an 
> idea how to deal with this. ile eventtheme aus solch einer Tabelle, dann 
> alle Umlaute defekt.
> * Export table to dbf:
>    + exporting tables to dbf created tables where original columns got 
> mixed up completely. The resulting table was not usable at all. Sorry to 
> say that.
> * TABLES in general
>   + it would be great, if integer values in xls/openoffice would be 
> displayed in gvSIG also as integer values. Right now, numbers always get 
> a ".0" at the end.
> * LINK:
>   + the link function is good, I would like to use it to identify false 
> values of a key column. For me, selecting more than one records in one 
> table was not reflected in the other table. Is this correct?
>
> Any comments or ideas are appreciated very much. I hope that these 
> issues can be reviewed within the stabilization process. I consider them 
> as very important, as they make are cruical for my work.
>
> Best,
> Wolfgang
>
>
>
>
>
>
>
>
>