[mapguide-users] SQL Server Provider vs. FDO Provider for a feature join...

[Dave Wilson]

The master database is the default when using SQLServer if I am not
mistaken. What login are you using to access the tables? It should be
one with at least select privileges against 1 or more tables within your
database. You should ensure you are using SQLServer authentication and
not windows.
 
Dave

  _____  

From: Warren Medernach [mailto:warren.medernach at imaginit.ca] 
Sent: Monday, October 30, 2006 7:51 AM
To: users at mapguide.osgeo.org
Subject: RE: [mapguide-users] SQL Server Provider vs. FDO Provider for a
feature join...


Ok, I got a little further on this...
 
In my ODBC Connection I was changing the 'default database' to use my
dbase, and doing this it wouldn't show me any tables.  If I toggle this
'Off', it then shows me the master db tables...
 
I'm starting to wonder if this is a 'permissions' issue with my db?
 
Warren
 

  _____  

From: Warren Medernach [mailto:warren.medernach at imaginit.ca] 
Sent: Monday, October 30, 2006 8:37 AM
To: users at mapguide.osgeo.org
Subject: RE: [mapguide-users] SQL Server Provider vs. FDO Provider for a
feature join...


Thanks for the Info Keith!
 
Did you need to specify or change any settings in your ODBC connection?
Are you using SQL Server or NT Authentication in the ODBC connection?
What credentials are you using on the MapGuide Studio side?
 
I don't know what else to try?
It won't 'Show' me the tables, or save the Coord Sys with the Connection
in Studio?....
 
Warren


  _____  

From: Campbell, Keith A [mailto:keith.campbell at atkinsglobal.com] 
Sent: Monday, October 30, 2006 8:01 AM
To: users at mapguide.osgeo.org
Subject: RE: [mapguide-users] SQL Server Provider vs. FDO Provider for a
feature join...


Hi Warren,
 
I'm not sure that this is going to be much help other than to confirm
that you should be able to do what you want. I can't see anything you're
doing wrong based on your description.
 
Firstly, yes, the ODBC option is the way to go to create your join. 
 
I have got this arrangement working, though I have not had the problem
you mention regarding assignment of the coordinate system. I've saved an
arbitrary coordsys in my data connection and everything works. 
 
Are you using version 1.0.2? It has a number of enhancements in this
area. 
 
I've also found that if the SQL database is not local to the MapGuide
Service, this significantly impacts the performance, making
configuration of the join / layer frustrating to say the least.
 
Keith

  _____  

From: Warren Medernach [mailto:warren.medernach at imaginit.ca] 
Sent: 27 October 2006 16:50
To: users at mapguide.osgeo.org
Subject: RE: [mapguide-users] SQL Server Provider vs. FDO Provider for a
feature join...


Correction...
Subject should read:  SQL Server FDO Provider vs. ODBC Provider...
 
Warren

  _____  

From: Warren Medernach [mailto:warren.medernach at imaginit.ca] 
Sent: Friday, October 27, 2006 9:01 AM
To: users at mapguide.osgeo.org
Subject: [mapguide-users] SQL Server Provider vs. FDO Provider for a
feature join...


Hello all,
 
I want to create a join from and SDF feature source, to a SQL Server
database.
I read in the list that the SQL Server FDO Provider is only for
accessing datastores within SQL Server (datastores created with Autodesk
Map).  
 
So, that would leave the ODBC Provider to connect to SQL Server for the
join.  However, I cannot get this to work...  I can choose the ODBC
Provider, and specify the DSN to my SQL Server, Test Connection is
successful, but when I try to set the coordinate system, this is never
'saved'.  This causes a problem, as it seems to give an error anytime
you try to join a feature source that doesn't have a coordinate system
assigned.
 
Btw, I was successful in getting this to function with an Access
dbase...
Any help and/or guidance would be greatly appreciated.
 
Warren Medernach


This message has been scanned for viruses by MailControl
<http://bluepages.wsatkins.co.uk/?4318150> 



This email and any attached files are confidential and copyright
protected. If you are not the addressee, any dissemination of this
communication is strictly prohibited. Unless otherwise expressly agreed
in writing, nothing stated in this communication shall be legally
binding. <http://www.blackspider.com/> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/mapguide-users/attachments/20061030/7f01ab22/attachment.html