I just want to check with the user community that what I see is indeed what ESRI think should be happening...
So following the instructions here I connect with an OLE connection to an Access database (accdb). I add the table to the map and then create an event theme from it, so far so good, as shown below.
Using the select tool I draw a selection box around 1 point on the map an I see this...
All points selected!
So I open the attribute table of the event layer and I see this...
Nothing is selected!
Am I right to conclude that an OLE connection does not work well with arcpro and that one cannot create sensible event themes from a table coming out of an accdb?
Solved! Go to Solution.
Good news Chris was able to identify this odd behaviour, hopefully documentation and/or tool will be updated with a warning as the solution was quite trivial. The table in the accdb had a unique ID field but it also needs to be set within Access to be the PRIMARY KEY. Once this was done and you build an event layer from it then rows are treated as single features and you can select individual feature and zoom to them.
Hello @DuncanHornby , no that would not seem to be the expected behaviour, and the instructions you have followed appear to be correct.
Can you post an anonymous sample .accdb file for us to try ?
Hi @ChrisUnderwood , just checking if I can share a sample of the database, if I can't I will try to spoof up something. Either way will get back to you as this is a real show stopper for us and stopping a major project in our team from migrating away from ArcMap, where it just works flawlessly.
Dear @ChrisUnderwood,
Attached is a zip file with an access database, points have been deliberately moved but the same issue still persists.
It will be interesting to hear if you get the same issues and if there is a solution? By the way I using ArcPro 3.3.
Duncan
Yes, I see exactly what you have described too. I can't see any immediate answer to it, but I'll carry on looking.
The problem is not specific to your data, and it is not specific to the BNG Coordinate System. But I don't know what the problem is, it could be a Bug. I suggest you log a case with your Esri Distributor for more investigation.
Have logged it with ESRI UK.
Good news Chris was able to identify this odd behaviour, hopefully documentation and/or tool will be updated with a warning as the solution was quite trivial. The table in the accdb had a unique ID field but it also needs to be set within Access to be the PRIMARY KEY. Once this was done and you build an event layer from it then rows are treated as single features and you can select individual feature and zoom to them.