[GRASS-user] Multiple attribute tables in winGRASS 6.4

[Colin Nielsen]

I've just uploaded a new version (r38959) with ODBC support enabled.
Please test it out and let us know if it is working properly. I hope
this solves your issue Sharon. (Please remember that it can take up to
24 hours before the new updates make it to all the web mirrors).

-Colin

On Fri, Sep 4, 2009 at 2:54 AM, Sharon M<morrisxs09 at gmail.com> wrote:
> Hi,
>
> I'm hoping the general GRASS mailing list community can help me.
>
> I'm using winGRASS 6.4 (r38875) on windows XP and using DBF files
> (oracle and ODBC is not currently supported in winGRASS).
>
> I'm able to connect an additional attribute table containing
> alternative names to a vector map. The cat columns in layer 1 and
> layer 2 are the same (numbers 1-25). e.g.
>
>> v.db.connect map=locn layer=2 key=cat table=locn_tbl2
>
> If I bring up the attribute window manager, I can see the new table is
> in layer 2.
>
>> v.info    reports that there are 2 db links.
>
>> v.info -c map=locn layer=2   reports list of columns in layer 2
>
> However, commands such as v.label, d.vect.thematic, d.vect, v.extract,
> etc are unable to access layer 2. Also, if using the windows which
> pop-up (instead of the command line) for any of these commands, you
> cannot change the layer option from "1" to "2" (or any other layer
> value).
>
> example output...
>> v.label labels=alt_nme map=locn col=othnme layer=2
> gives error...  "Sorry, <col=> is ambiguous"
>
> Does anyone have any ideas as to whether multiple layers works in winGRASS?
>
> Thanks in advance,
>
> Sharon
> _______________________________________________
> grass-user mailing list
> grass-user at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-user
>