Aside from Spatialite, you might also want to consider PostGIS. Think of it as Spatialite's big brother ;-) It's just another data source for QGIS while you can connect to it using the RODBC package in R.
Note there are two ways of doing this. The way you are going about doing it is the long way but that is the way I am going to show how to do it here. The other way is by just going to Add Vector Layer and then selecting file and then browsing to where your .mdb file is located and opening the .mdb file.
First, you need to make sure QGIS 32 bit version is ...
Not sure if you will be able to work with MS Access in QGIS (plus I haven't heard about any respectable GIS-project that would use MS databases); MSSQL - is supported (but never tried it myself and never will ;-) ).
Consider possibility to use Spatialite (spatial extension of SQLite). It will be quite suitable to operate Spatialite DB in QGIS and you can ...
It's possible to connect via ODBC.
In windows, start the ODBC Administrator and define your Datasource (Microsoft Access Driver).
In QGIS go to Layer/Add Layer/Vector Layer/database: Type=ODBC.
Set up a new Connection. Host should be "localhost" if your database
is local on your machine. Database Name is the same name you defined before in the ODBC ...
With the new "Processing" tools available in QGIS 2, this becomes a bit easier. While I have still not found a way to "live-link" the data (so that if you change the values in the MS Access table, the point moves automatically), this method seems to work pretty well.
Credit goes to "Christina" and "Bernd" in the comments section of this page (and of course ...
I think you should take into account that personal geodatabase is created and accessed through ESRI clients, following proprietary patterns. MsAccess is not a spatial database on its own (it does not provide a spatial data model, so obviously no spatial data loading capabilities, spatial indexing or extended spatial SQL), so ESRI manages spatial information ...
Your best bet is to keep your geometry in shapefiles and keep the data in access. Just make sure there is a common ID in both tables. Both QGIS and Mapinfo support joining shapes to database features (eg accessed via odbc). In Mapinfo, check the function "geocode".
The ArcGIS 10.1 Help indicates you cannot edit the attributes of Excel or MS Access files, added through an Ole DB connection, because they have no ObjectID field. You can Copy the data to a fGDB table and then edit it. Or you can script Python to edit the native MS formats.
By default the Postgres server is only accessible from the same computer it runs on.
You need to setup the Postgres server to listen not just locally, but on your internet facing network card too. This is done in the postgresql.conf configuration file.
You will also need to enable user authentication from the outside, which is done ...
Personal geodatabases--really anything with Access--have a ton of limitations. File geodatabases permit up to 65,534 fields per table/feature class.
It should be no problem to import your existing data to a file geodatabase and then make the changes/additions that you need.
To save yourself a bit of code you could use the geoprocessor and call DataManagementTools.CopyRows. See also: How to run a geoprocessing tool
// Create the geoprocessor.
Geoprocessor GP = new Geoprocessor();
// Create the tool process object.
ESRI.ArcGIS.DataManagementTools.CopyRows copyrowsTool = new
Keep in mind that QGIS 1.8 on Windows supports .mdb under Layer->Add Vector Layer...->Browse->and change the file type in the drop-down to the right of the "File name"" form field.
But.... QGIS 1.8 on OSX does not support opening of .mdb's (afaict)
You can do both, kinda. If you wanted, which would be a good thing to do, make a Personal Geodatabase (which is a MS Access DB). This will allow you to store all the spatial data and any tabular data in one DB. You will also be able to access the tables in MS Access. There are limitations, the ones imposed by MS Access; a large one being the 2GB size ...
I assume you are talking about manipulating an active ArcMap session from outside the application boundary. To do this you need to use IAppROT to get a reference to the specific ArcMap application instance you want to manipulate. From there you can access its document, active view, map, etc. and manipulate them as needed (see @artwork21's answer).
Just be ...
You have to use Mapinfo.Eval and MapInfo.Do and wrap the other requests. You can't simply call MapBasic functions in Integrated mapping, you need to do them through these two methods, if I remember correctly.
So, something like this:
If mapinfo.Eval("TableInfo(" & tabName & "," & 5 & ")") = "F" Then
MsgBox "Cannot open table!"
Esri's online help (see two links below as examples) discourages users from opening Personal Geodatabases stored in Microsoft Access using Access so I think your phrase "futile because pgdb technology is proprietary and no detailed publicly available knowledge exists" probably sums it up.
If you're looking to get your data into an access database you could skip the middle conversion step entirely (or rather have ArcGIS handle it for you) by transferring your data to a personal geodatabase, which in reality is an access database.
From ArcGIS you can use the Create Personal Geodatabase tool to create the access database, and then you should be ...
The thing to do these days would probably be to link to a map on ArcGIS Online. You could do this by providing a hyperlink to the Webmap viewer, https://www.arcgis.com/home/webmap/viewer.html?... It should be possible to pass parameters to set the center and scale of the map in the URL, see the documentation for more details.
A variation could be to embed a ...
If you're interested in PostGIS, you might want to visit the BostonGIS website. They have great material to get you started. You can also start with OpenGeo's introduction to PostGIS workshop.
PostGIS has a shapefile importer that you can use to load your shape files. As for your accdb files, you might want to convert them to SQL first. Bullzip has this ...
I had this exact same problem today. It wasn't permissions, it was weird characters in my data. As it turned out, I had pound signs (#) in the labels column and when I got rid of those, the shapefile export worked perfectly.
WARN: it seems the 'Join Attributes' function ha been removed from fTools 0.6.2, solution for me was to downgrade to 0.6.1.
You can use QGIS to perform the operation you want, please proceed as follows:
if not installed already, install Quantum GIS (an Open Source desktop GIS) and then install fTools as described here
export the mdb table or query into dbf ...
You should be able to use the AccessWorkspaceFactory co-class even though it's not a personal geodatabase. You could also use ADO.NET. I am not sure why your code isn't working but I do know that working with property sets is an exercise in frustration.
MS Access is not able to do spatial operations, at least not in the way those used to using OGR standard spatial databases may be familiar with.
Functions such as ST_Within, ST_Intersects and the dedicated geometry types simply don't exist.
Now, that's not to say that you can't work with co-ordinate values, but you'll have to treat them as normal decimal / ...
If I have this correct -- biggest constraint is that you must use the local municipal data as the geocoding reference data. This wasn't clear in your original question.
I'll give you the ArcGIS answer -- since that is available to you and what I know.
You need to create a ArcGIS locator from the municipal data, i.e. the reference data. This is your ...
Why dont you import the MS tables into a Geodatabase? Linking from a static MS database table may not produce the results you are looking for, as you will need/want to load the data (maybe multiple data layers) and open it into ArcMap. You may also what to symbolize these layers. If you are planning on viewing this in ArcMap, why not build a MXD project ...
You should be able to use the Copy Features Tool on the layer with your selection, as long as the out_feature_class parameter is set to the path on disk of where you want the shapefile to be written out it should just work.
No, the assumption was not correct (ArcObjects is calling the Access function, so there should be no difference).
Access-based geodatabases are "old school", with limitations in size and capability; their use has been greatly de-emphasized of late, especially in light of the deprecation of PGDB support on 64-bit platforms (no ArcGIS Server or Pro)