I have spent a few months upgrading a toolkit I created and is used extensively throughout our organisation of 2-3000 users. I used DTPicker controls as I found these were ideal.
My beloved organisation then upgraded to XP and decided that the standard desktop didn't need this control installed locally. My excel-based application no longer works.
I experimented with distributing the ocx file with the excel based application, and this worked for me. Problem is - it installs itself in the windows folder, and my beloved organisation prohibits almost all staff from writing to their hard drives.
So - I am left in a bit of a quandary. One line I am pursuing is registry setting changes that allows the ocx file to operate on a public drive and not self-install.
I have run searches on this and other forums (fora?) and not found anything that exactly matches what I am after.
Can anyone please advise me if there is a way to make mscomct2.ocx operate from a shared/public drive without self-installing to windows?
Many many thanks.