Thanks Andy,
I know what you are saying (but sure it was an Inner join) - I authored in
Studio and verified in Maestro but will try again especially if someone can
run through the steps below independantly. Meastro also has an
Associative join - do you know what that is?
Andy Morsell wrote:
Subject: RE: [mapguide-users] Feature Joins
Chris,
MGOS 1.2 did have some join issues and I believe you might be
encountering one of them. Are you doing an inner or outer join?
With MGOS 2.0 I have joined SDFs with Access many times in the following
cases:
Inner 1-1
Inner 1-Many
Outer 1
Are you expecting 2 features to be rendered in the map? Are you expecting to
see 2 property sets in the AJAX Viewer? It sounds like the former? I'm not sure
anyone has requested multiple features to appear as a result of a 1 to many
join. Users have wanted to see the multiple properties
Chris,
MGOS 1.2 did have some join issues and I believe you might be encountering one
of them. Are you doing an inner or outer join?
With MGOS 2.0 I have joined SDFs with Access many times in the following cases:
Inner 1-1
Inner 1-Many
Outer 1-1
Outer 1-Many
The above worked for my use cases
/429
Thanks,
Bruce
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bruce Dechant
Sent: Monday, February 11, 2008 2:24 PM
To: MapGuide Users Mail List
Subject: RE: [mapguide-users] Feature Joins absolutely broken in MGOS
2.0.0 RC1
I am using studio 2008. It would be a considerable effort to create a
portable example of the 'broken' joins - I will have to try to find some
time. I could easily provide an SDF which will not allow me to create a new
join. I will log a defect - thanks.
--
View this message in context:
:[EMAIL PROTECTED] On Behalf Of Jackie Ng
Sent: Tuesday, February 12, 2008 11:56 PM
To: mapguide-users@lists.osgeo.org
Subject: RE: [mapguide-users] Feature Joins absolutely broken in MGOS 2.0.0 RC1
3rd time does not seem to be the charm :(
RC3 still fails to render my test joined layers
The message The current feature source has no feature classes, and cannot
support joins is some strange message that MapGuide Studio spits out due to
some caching problem (I believe). If you restart the MapGuide Server after
breaking a join, you should be able to repair or create a new join.
But
I am having great difficulty with feature joins in RC 2. Migrated feature
joins are not working Studio will not allow me to create a feature join
because it erroneously reports that The current feature source has no
feature classes, and cannot support joins even though the same feature
source
Restarting the server doesn't seem to help for me. I agree w/you: I hope
this is resolved in the final version - joins are critical to my sites and I
can't upgrade if it breaks my existing sites.
--
View this message in context:
There is a known issue with feature joins in RC1.
It is being looked at.
Thanks,
Bruce
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jon Rizzo
Sent: Monday, February 11, 2008 9:58 AM
To: mapguide-users@lists.osgeo.org
Subject: Re: [mapguide-users
Hi Jon,
What version of Studio are you using to access the RC?
Would it be possible for you to put together a portable data set (MGP
file + local Access database?) and script for reproducing this problem
so that we can figure out what is causing the problem?
Jason
To: MapGuide Users Mail List
Subject: RE: [mapguide-users] Feature Joins absolutely broken in MGOS 2.0.0 RC1
There is a known issue with feature joins in RC1.
It is being looked at.
Thanks,
Bruce
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jon Rizzo
Sent
This is a known issue I will be looking at next week.
Thanks,
Bruce
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jackie Ng
Sent: Monday, January 28, 2008 8:25 PM
To: mapguide-users@lists.osgeo.org
Subject: [mapguide-users] Feature Joins absolutely
14 matches
Mail list logo
