[mapguide-users] Maestro: can't find the table containing the
geometry field with SQLServerSpatial
brent.robinson at autodesk.com
Wed Oct 15 12:36:57 EDT 2008
This is a known defect that was fixed in July. The fix provides almost full support for the varchar(max) and nvarchar(max) columns. There's one limitation: when selecting from these columns, values longer than 16000 characters are truncated.
The FDO 3.3.2 SQLServerSpatial provider should have the fix. It can be obtained from the Windows SDK download at http://fdo.osgeo.org/content/fdo-332-downloads. You'd just need to extract the following DLL's:
to MapGuide's FDO bin directories:
Program Files\Autodesk\MapGuideStudio2009\FDO (if present)
I'd recommend saving copies of your current versions of these DLL's before extracting, just in case.
I have MG enterprise on my machine so your directories might look a bit different.
If you get a chance to try this out, please let me know if it fixes the problem.
From: mapguide-users-bounces at lists.osgeo.org [mailto:mapguide-users-bounces at lists.osgeo.org] On Behalf Of Carl
Sent: Wednesday, October 15, 2008 10:28 AM
To: mapguide-users at lists.osgeo.org
Subject: RE: [mapguide-users] Maestro: can't find the table containing the geometry field with SQLServerSpatial
Brent Robinson-5 wrote:
> Hi Carl,
> Do any of your tables have a varchar(max) column?
View this message in context: http://www.nabble.com/Maestro%3A-can%27t-find-the-table-containing-the-geometry-field-with-SQLServerSpatial-tp19977173p19994687.html
Sent from the MapGuide Users mailing list archive at Nabble.com.
mapguide-users mailing list
mapguide-users at lists.osgeo.org
More information about the mapguide-users