The problem you are describing is FDO specific, which is an underlying layer of MapGuide...
but, b4 we go that far over to fdo-users, your original post was missing the information like is the exact version of the native client, plus the xml definition of your feature source, ie it could be the connection parameters are simply wrong? z On 10 June 2010 11:47, David Collins <[email protected]> wrote: > At the moment, the problem description is very tied to MapGuide. > Can you (or someone) tell me how to simplify the problem for the benefit of > the FDO-users list? > ie. Can I use some lower-level FDO utility to try to create the SQL > connection, that doesn't involve the MapGuide software? > > > On Thu, Jun 10, 2010 at 11:21 AM, Zac Spitzer <[email protected]> wrote: >> >> I'd suggest posting this question on fdo-users as it's a specific FDO >> question >> -- >> Zac Spitzer >> Solution Architect / Director >> Ennoble Consultancy Australia >> http://www.ennoble.com.au >> http://zacster.blogspot.com >> +61 405 847 168 > > > _______________________________________________ > mapguide-users mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/mapguide-users > > -- Zac Spitzer Solution Architect / Director Ennoble Consultancy Australia http://www.ennoble.com.au http://zacster.blogspot.com +61 405 847 168 _______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users
