<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>RE: [mapguide-users] RE: ODBC problem...</TITLE>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.5335.5" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=546491518-19042006><FONT face=Arial
color=#0000ff size=2>I agree that the options and flexibility are good and that
making your primary the spatial datasource is the most intuitive. It's
just confusing from a UI standpoint. In this case, I defined a
primary ODBC datasource and I create an extension off of that to a secondary
spatial datasource (SDF). I then create new layer from that, choose
my extension as the feature class, and then I can select the geometry from the
secondary as the Geometry (it's the only geometry in this case since there is
none defined in the primary). Studio even detects the type of
geometry (polygon) and sets up its default style parameters
accordingly. I would expect this layer to work and display just as if I
had done it the other way around since the geometry is available for me to
choose when defining the layer. </FONT></SPAN></DIV>
<DIV> </DIV><!-- Converted from text/rtf format -->
<P><SPAN lang=en-us><FONT face=Tahoma size=1>Andy </FONT></SPAN><BR></P>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Dave Wilson
[mailto:dave.wilson@autodesk.com] <BR><B>Sent:</B> Wednesday, April 19, 2006
11:14 AM<BR><B>To:</B> users@mapguide.osgeo.org<BR><B>Subject:</B> RE:
[mapguide-users] RE: ODBC problem...<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=ltr align=left><SPAN class=308150818-19042006><FONT face=Arial
color=#0000ff size=2>One of the features of having the join on the ODBC resource
is that you could chain multiple Attribute tables together if you needed to
rather than combining the data in a table or view. Of course the more you chain
together the slower your performance will likely be.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=308150818-19042006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=308150818-19042006><FONT face=Arial
color=#0000ff size=2>Chaining the spatial to spatial or attribute to spatial
doesn't make sense for the most part I agree although you could join an SDF to
an SHP to get attributes if you really didn't want to merge the data, but I'm
not sure how likely that case would be. Of course I could argue then I have a
POINT source in ODBC and join it to an SHP for attrbutes, but again would you
really want to do it?</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=308150818-19042006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=308150818-19042006><FONT face=Arial
color=#0000ff size=2>I think the options are there for
flexibility.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=308150818-19042006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=308150818-19042006><FONT face=Arial
color=#0000ff size=2>Dave</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Andy Morsell
[mailto:amorsell@spatialgis.com] <BR><B>Sent:</B> Wednesday, April 19, 2006
12:06 PM<BR><B>To:</B> users@mapguide.osgeo.org<BR><B>Subject:</B> RE:
[mapguide-users] RE: ODBC problem...<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=ltr align=left><SPAN class=296394917-19042006><FONT face=Arial
color=#0000ff size=2>Thanks for the clarification Dave. I hadn't even
looked at my spatial datasource to notice that there is no</FONT></SPAN><SPAN
class=296394917-19042006><FONT face=Arial color=#0000ff size=2>w a Join portion
of the dialog at that level. I was thinking the join was only defined from
the tabular datasource. Now that I have set it up there (pretty much using
the same steps I previously outlined) it is working fine. I can display my
parcel polygons with tooltips and properties derived from the secondary Access
database.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=296394917-19042006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=296394917-19042006><FONT face=Arial
color=#0000ff size=2>It is a little confusing that it can be done the other way
around and that a layer can be seemingly created from that while choosing the
geometry feature from the secondary datasource. That process should
probably be changed in Studio to prevent that from
happening.</FONT></SPAN></DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV>
<DIV><SPAN class=296394917-19042006><FONT face=Arial color=#0000ff size=2>I'm
still having problems with point data from an ODBC resource, but will do some
more experimenting later.</FONT></SPAN></DIV><!-- Converted from text/rtf format -->
<P><SPAN lang=en-us><FONT face=Tahoma size=1>Andy </FONT></SPAN><BR></P>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Dave Wilson
[mailto:dave.wilson@autodesk.com] <BR><B>Sent:</B> Wednesday, April 19, 2006
7:26 AM<BR><B>To:</B> users@mapguide.osgeo.org<BR><B>Subject:</B> RE:
[mapguide-users] RE: ODBC problem...<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=ltr align=left><SPAN class=043431814-19042006><FONT face=Arial
color=#0000ff size=2>Am I correct in understanding you are using the spatial
resource as the Secondary resource? The Spatial resource needs to be the primary
resource if this is what the layer is to be based on. The join is generally for
attaching attribute data to spatial data such as adding properties from an
Access table to an SDF.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=043431814-19042006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=043431814-19042006><FONT face=Arial
color=#0000ff size=2>Point data from an ODBC resource should also work as a
primary resource.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=043431814-19042006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN><SPAN class=043431814-19042006><FONT
face=Arial color=#0000ff size=2></FONT></SPAN><SPAN
class=043431814-19042006><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=043431814-19042006><FONT face=Arial
color=#0000ff size=2>Dave Wilson</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Andy Morsell
[mailto:amorsell@spatialgis.com] <BR><B>Sent:</B> Tuesday, April 18, 2006 6:22
PM<BR><B>To:</B> users@mapguide.osgeo.org<BR><B>Subject:</B> RE:
[mapguide-users] RE: ODBC problem...<BR></FONT><BR></DIV>
<DIV></DIV><!-- Converted from text/rtf format -->
<P><SPAN lang=en-us><FONT face=Arial size=2>Here are the steps I took to create
the join. Note that I wasn't able to do with anything with the join in
terms of creating a layer from it, however.</FONT></SPAN></P>
<UL>
<LI><SPAN lang=en-us><FONT face=Arial size=2>Once your datasource is setup and
you can see the tables listed in the Refine Data Setup area, click the New
Extended Feature Class button. </FONT> </SPAN>
<LI><SPAN lang=en-us><FONT face=Arial size=2>Choose your other datasource in
the repository that you are connecting to</FONT><FONT face=Arial size=2>
</FONT></SPAN>
<LI><SPAN lang=en-us><FONT face=Arial size=2>Choose the Primary Feature class
(table)</FONT></SPAN>
<LI><SPAN lang=en-us><FONT face=Arial size=2>Click on your New Join below the
Extension you just created</FONT></SPAN>
<LI><SPAN lang=en-us><FONT face=Arial size=2>You will most likely only have
one option for the Secondary class (table)</FONT></SPAN>
<LI><SPAN lang=en-us><FONT face=Arial size=2>Select your Primary Column and
Secondary Column fields. These are the key fields tying together your
primary (tabular) and secondary (spatial) datasources.</FONT></SPAN>
<BR></LI></UL>
<P><SPAN lang=en-us><FONT face=Arial size=2>If you get this far, please let us
know if you can successfully create a layer where you can view the resultant
objects. I also tried creating a layer from X and Y points in a table from
this database and, again, was not able to view the resultant
geometry.</FONT></SPAN></P><BR>
<P><SPAN lang=en-us><FONT face=Arial size=2>Andy Morsell</FONT></SPAN> </P>
<P><SPAN lang=en-us><FONT face=Arial size=2>-----Original
Message-----</FONT></SPAN> <BR><SPAN lang=en-us><FONT face=Arial size=2>From:
Thud732 [</FONT></SPAN><A href="mailto:devlin.fung@sapience360.com"><SPAN
lang=en-us><U><FONT face=Arial color=#0000ff
size=2>mailto:devlin.fung@sapience360.com</FONT></U></SPAN></A><SPAN
lang=en-us><FONT face=Arial size=2>] </FONT></SPAN><BR><SPAN lang=en-us><FONT
face=Arial size=2>Sent: Tuesday, April 18, 2006 4:30 PM</FONT></SPAN> <BR><SPAN
lang=en-us><FONT face=Arial size=2>To: users@mapguide.osgeo.org</FONT></SPAN>
<BR><SPAN lang=en-us><FONT face=Arial size=2>Subject: [mapguide-users] RE: ODBC
problem...</FONT></SPAN> </P><BR>
<P><SPAN lang=en-us><FONT face=Arial size=2>Hi Andy:</FONT></SPAN> </P>
<P><SPAN lang=en-us><FONT face=Arial size=2>Can you please outline your 'join
connection' steps? I was able to establish a successful test connection, but
failed when joining.</FONT></SPAN></P>
<P><SPAN lang=en-us><FONT face=Arial size=2>Thank you.</FONT></SPAN> <BR><SPAN
lang=en-us><FONT face=Arial size=2>TC</FONT></SPAN> <BR><SPAN lang=en-us><FONT
face=Arial size=2>--</FONT></SPAN> <BR><SPAN lang=en-us><FONT face=Arial
size=2>View this message in context: </FONT></SPAN><A
href="http://www.nabble.com/Failed-to-test-the-Web-Server-Extensions-after-installation-t1432431.html#a3978903"><SPAN
lang=en-us><U><FONT face=Arial color=#0000ff
size=2>http://www.nabble.com/Failed-to-test-the-Web-Server-Extensions-after-installation-t1432431.html#a3978903</FONT></U></SPAN></A><SPAN
lang=en-us></SPAN></P>
<P><SPAN lang=en-us><FONT face=Arial size=2>Sent from the OSGeo MapGuide forum
at Nabble.com.</FONT></SPAN> </P><BR>
<P><SPAN lang=en-us><FONT face=Arial
size=2>---------------------------------------------------------------------</FONT></SPAN>
<BR><SPAN lang=en-us><FONT face=Arial size=2>To unsubscribe, e-mail:
users-unsubscribe@mapguide.osgeo.org</FONT></SPAN> <BR><SPAN lang=en-us><FONT
face=Arial size=2>For additional commands, e-mail:
users-help@mapguide.osgeo.org</FONT></SPAN> </P></BODY></HTML>