[mapguide-users] Fwd: [OSGeo-Discuss] Why does OSGeo FDO Provider for SQL Server Spatial try to access the wrong database?

[Bruno Scott]

There is some HomeMade builds that you could try out.
There are 3 tickets fixed in these build:  766
<http://trac.osgeo.org/fdo/ticket/766>  , 876
<http://trac.osgeo.org/fdo/ticket/876>  , 875
<http://trac.osgeo.org/fdo/ticket/875>  

You can download here

fdo 3.8 x64
<http://www.geomapgis.com/web/geomap-group/fdo/SqlServerSpatial/3.8/x64/SQLServerSpatialProvider.zip>  
fdo 3.8 win32
<http://www.geomapgis.com/web/geomap-group/fdo/SqlServerSpatial/3.8/win32/SQLServerSpatialProvider.zip>  
fdo 3.7 x64
<http://www.geomapgis.com/web/geomap-group/fdo/SqlServerSpatial/3.7/x64/SQLServerSpatialProvider.zip>  
fdo 3.7 win32
<http://www.geomapgis.com/web/geomap-group/fdo/SqlServerSpatial/3.7/win32/SQLServerSpatialProvider.zip>  

Bruno



--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Fwd-OSGeo-Discuss-Why-does-OSGeo-FDO-Provider-for-SQL-Server-Spatial-try-to-access-the-wrong-databas-tp5078593p5080148.html
Sent from the MapGuide Users mailing list archive at Nabble.com.