Hi there,
In the setup I use at Ashburton District Council, SSA is connected directly to the MapInfo DB.
I have seen some info on the web where users seem to be using static tab files and DB connected linked, layers of some form within SSA. This is a good way to get data into SSA, but not the only way to work with DB.
(For us the MapInfo DB is the definitive source for GIS data; the tables within it are used to create static tables on the network for general consumption. Any data creators / editors use DB linked tables – again for general access their layers are created in static form on the network.)
- With SSA If your tab files are built directly from your DB source, you can change the data source for your layers in SSA to point at your MapInfo DB equivalent layers.
(The DB attribute columns shouldn’t be changed after that, pretty certain they can be added to – although the extra columns will not appear in SSA as they haven’t been referenced in the static tab version)
- SSA will pull your data directly from your MapInfo DB.
- Any edits that are made by linked table users will show in SSA after they have committed changes.
You can also now go ahead and configure editing templates to be able to edit your DB data within the SSA GUI, it works well.
Note: if you need to make changes to how the layers look, either edit the namedlayer xml using webdav or use MapInfo to upload the layers again – note: when you refresh the layers again the data source will revert back to the static version you have loaded in MapInfo, but it only takes a few minutes to swap the data source back to the DB.
cheers