I was wondering if that might be the case. Finally, after several updates on vista and a service pack, I got the Native client installed and all works as expected. Thanks for the info Jackie.
Rich On Mon, Jul 15, 2013 at 8:15 PM, Jackie Ng <[email protected]> wrote: > The FDO provider for MGOS 2.2 internally used the out-of-the-box SQL Server > ODBC driver, which is why this error never occurred. > > It is now internally using the SQL Server Native Client ODBC driver so the > FDO provider can work with bigger geometries. > > You should install the SQL Server Native client on the machine where the > MapGuide Server is installed, as that is where it is trying to make the FDO > connection from. > > - Jackie > > > > -- > View this message in context: > http://osgeo-org.1560.x6.nabble.com/SQL-Spatial-on-MGOS-2-5-tp5066541p5066622.html > Sent from the MapGuide Users mailing list archive at Nabble.com. > _______________________________________________ > mapguide-users mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/mapguide-users >
_______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users
