Helmut, Thank you; I did try 'date' and got the same result using the exact dataset. After sending out the email (thinking GRASS *might* be choking on the number of columns), I reduced the number of columns and re-ordered them (thinking that maybe the ID ought to come first -- also recognizing that this should NOT be the case). I got the same error -- then, I did as you have suggested, using 'datetime' instead of 'time' -- this worked. So, it almost certainly was the use of 'time' or 'date' as a column name...
At some point I'll go back to the original dataset to verify this. Thank you... Best, Tom On Thu, Jan 19, 2017 at 3:27 PM, Helmut Kudrnovsky <hel...@web.de> wrote: > >SQL parser error (syntax error, unexpected TIME, expecting > >NAME processing 'time') in statement: > > Could it be that time is a SQL reserved word/key? Try another word instead > of 'time'. > > HTH > Helmut > > > > ----- > best regards > Helmut > -- > View this message in context: http://osgeo-org.1560.x6. > nabble.com/GRASS-7-2-v-in-ascii-error-tp5304079p5304089.html > Sent from the Grass - Users mailing list archive at Nabble.com. > _______________________________________________ > grass-user mailing list > grass-user@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/grass-user --
_______________________________________________ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user