Search for an answer, post a question, or answer other users' questions in our GeoMedia support discussions. This discussion board is a great way to collaborate with industry peers around the world. It is intended for discussion and support of the GeoMedia Desktop and Add-on applications.
I have a situation of a costumer saying that the geowokspaces created with GeoMedia 2015, in machines with Windows 8.1, after a migration to Windows 10 (keeping GeoMedia in version 2015 ) don't show the geometries of the feature classes (only the attributive data is available).
The data is in SQL Server Spatial.
I've tested the situation in our machines, in versions 2015 and 2018, and the behaviour is the same as reported by the costumer.
Has anyone experienced a situation like this? Is there any solution for this (apart from saving the geoworkspace contents to a library and then deploying those contents in a new empty geoworkspace, situation in which the geometries become visible)?