Nasty question for y’all.
I have developed and maintain an Excel-based application that is used extensively across my organisation of a few thousand staff. I recently upgraded the application, and changed some of the controls used. I installed a datepicker control that was valid at the time, using a file mscomct2.ocx.
After starting this, we upgraded to XP, and this file disappeared from all clients. At the same time, the ability for anyone (save power-users such as myself) to write to their hard-drive was removed.
Now when the application is run, anyone other than myself gets a compile error because the ocx file doesn’t exist. If I release the application together with the ocx file, the ocx file tries to install itself on the user’s hard drive, and fails because of the poxy restricted permissions.
Questions:
Is there a generic ocx file that provides a datepicker control? I don’t particularly want to use a calendar control if I can avoid it.
Is there a way I can edit an ocx file so that it does not self-install? Or any other way of making the ocx file operate from the same public location as the application?
Is there a way of convincing a large nationwide organisation that their ideas of standardising desktops and servers, and their ideas of what staff should be allowed to do are moronic?
Many thanks.
Gravey.
