Hello again,
yesterday I had to revert my application to MapWinGis.ocx 4.8.8.1 after having installed it with MapWinGis.ocx 4.9.3.5 at a customer yesterday.
The application was so slow, that it paralyzed the computer for more than 5 minutes - the reverted version needs only a second for the same action. I'm completely aware that MapWinGis.ocx is not meant to work with access/vba and my code may not be optimal in places, but for future releases it would be nice to optimize the ocx code for performance. The bottle neck seems to be, as far as I can see, the index creation, if unique values are needed (which worked fine with 4.8.8.1).
I'm happy with 4.8.8.1 for the time being.
Thanks again for your excelent work.
Helmut
yesterday I had to revert my application to MapWinGis.ocx 4.8.8.1 after having installed it with MapWinGis.ocx 4.9.3.5 at a customer yesterday.
The application was so slow, that it paralyzed the computer for more than 5 minutes - the reverted version needs only a second for the same action. I'm completely aware that MapWinGis.ocx is not meant to work with access/vba and my code may not be optimal in places, but for future releases it would be nice to optimize the ocx code for performance. The bottle neck seems to be, as far as I can see, the index creation, if unique values are needed (which worked fine with 4.8.8.1).
I'm happy with 4.8.8.1 for the time being.
Thanks again for your excelent work.
Helmut
