what version of Map3D do you have?
- alfred -
*** 1 ***
I don't think it will solve your problem but it's better !
Have you installed the SP 2.1 for MAP 2013 ?
*** 2 *** The bad news
I have found sometimes strange bugs/limitations with joins with MAP 2013 (even with SP 2.1)
And I have not the same problem with MAP 2012 (+ SP 2), so ...
Maybe it's your problem !, Not sure at all !
Can you do a test with MAP 2012 + SP 2 or with MAP 2014 + SP 1 ?
Have you done the same join with an older MAP ?
>> If I export that same Shapefile to an SDF and THEN try the same join and filter
Tested that and sorry to say:
Sometimes it makes a difference depending on how the primary key or index is defined in SQL-Server, but with a little bit playing I have not got a solution now, sorry.
In some situations it might be an option to load the SHP, run the joining and export that as new SDF ... because then you have the data if the joined fields transfered from SQL_Server into your SDF.
The advantage is then
The disadvantage might be
This image shows the joined options, 2 fields in the SDF (+ 1 for geometry) and the rest is from relation to data from SQL-Server ==> and the query dialog does not show the additional fields.
- alfred -
PS: I have tested with AutoCAD Map3D 2013 (G.114 HF1), AutoCAD Map3D 2014 (I.108 SP1) ... all German ... on Win7x74 with SQL-Server 2012 (64bit)
There is an issue that I have reproduced on Map 3D 2014 (with SHP joined to ODBC) that might also be the cause of the issue you report. It is being tracked as DE1705 internally. I call it "Impossible to label using joined fields". Basically when you got to Style Editor > Style Label > and choose Expression to build an expression to label features, only the native fields 'stick'; when the Expression includes fields from the joined attributes, the Expression changes itself unexpectedly after hitting OK to leave the Create/Modify Expressions window.
This is nominated for a fix but unfortunately I do not know if/when/how a fix will be produced or released.
I hope this helps to at least confirm the behavior that you are seeing.
Hello Autodesk & Everyone (from France)
An other bug/problem maybe linked to the ODBC problem ...
Today I haven't any MAP and Oracle to check again, sorry !
But If I remember well when doing double join (this means join on a Oracle Table and join again on a other Oracle table)
With MAP 2013 (and may be with MAP 2014) I can't use any field coming from the double join (second table) to do something ...
But I can use fields coming from the first join ...
And with MAP 2012 : no problem !
So I think it could be linked to the general problem of join with ODBC !
Waiting for your answer ...
PS: I know, it's bad to do that ! - A good view from Oracle could be the solution !?
Access a broad range of knowledge to help get the most out of your products and services.