[GRASS-dev] [GRASS GIS] #1629: v.in.db - odbc-driver - access-database: not working
GRASS GIS
trac at osgeo.org
Fri Sep 7 00:36:26 PDT 2012
#1629: v.in.db - odbc-driver - access-database: not working
--------------------------------+-------------------------------------------
Reporter: hellik | Owner: grass-dev@…
Type: defect | Status: new
Priority: critical | Milestone: 6.4.3
Component: Database | Version: svn-releasebranch64
Keywords: wingrass, db, odbc | Platform: MSWindows Vista
Cpu: x86-32 |
--------------------------------+-------------------------------------------
Comment(by mlennert):
Replying to [ticket:1629 hellik]:
> v.in.db driver=odbc database="C:\wd\access\testinput.mdb"
table=grassinput key=ID x=xcoor y=ycoor output=mdbvector
AFAIK, this is wrong usage of the odbc driver. database should not be the
path of the mdb file, but rather the name you give to the database in the
ODBC configuration.
This is what the message in German actually says:
"[Microsoft][ODBC Driver Manager] Der Datenquellenname wurde nicht
gefunden", i.e. The name of the source of data could not be found. Note
that it doesn't say that the _file_ hasn't been found, but the _name_.
ODBC is an intermediate layer which allows clients to communicate with
database in a standardized language. This means that clients do not
connect to the database directly, but via ODBC. In order to be able to
connect, you have to configure this connection using dedicated tools (IIUC
in MS Windows the tool is currently called "ODBC Data Source
Administrator") and give a name to that connection. You then use that name
as database name when accessing from a client via odbc.
I believe that unless there is more info about the ODBC access failing
when used correctly, this bug should be closed as invalid.
Moritz
--
Ticket URL: <http://trac.osgeo.org/grass/ticket/1629#comment:5>
GRASS GIS <http://grass.osgeo.org>
More information about the grass-dev
mailing list