I am pretty sure I am aware of the problem here - I have a DTPicker date control on a form which requires a reference to at least MSComCt2.ocx.
It seems by chance that my computer had this file so I used the control, but any new computers in our company (they are installed with XP still) do not have this control.
Also randomly MSCOMCTL.OCX is also missing.
I have read things like
http://www.accessmvp.com/djsteele/AccessReferenceErrors.html
http://www.access-programmers.co.uk/forums/showthread.php?t=43921
http://support.microsoft.com/kb/824255
But as microsoft does not seem to give support for it anymore http://support.microsoft.com/kb/297381 This problem will remain.
So as I am distributing a front end (a folder which contains the front end mde and other files) I thought I could simply include these two OCX files in there and all would be good. It seems that this allows my program to start (normally it does not even start) but as soon as you call the form which contains the control it says that the control is missing. (I am assuming this is because it is not registered in this folder)
As far as I can work out I do not have an option of late binding.
Up until now I have done the most written solution which is go to the problem computer and copy the OCX's into C:\WINNT\system32 (i have never needed to register it though) but this solution is not a long term one.
No offence but I prefer not to use the datepicker that has been developed here in the forum.
My first question is that such a control seems normal/essential for access surely when microsoft stopped distributing it, they offered something new. Did they? What is it?
If there is no replacement, then I know the problem, I have the OCX files, how should I make sure when a computer starts my program that does not by default have these files, reference them somehow. Should I simply distribute them with my front end and at start up do a file FILECOPY to C:\WINNT\system32 if the file is not there?
It seems by chance that my computer had this file so I used the control, but any new computers in our company (they are installed with XP still) do not have this control.
Also randomly MSCOMCTL.OCX is also missing.
I have read things like
http://www.accessmvp.com/djsteele/AccessReferenceErrors.html
http://www.access-programmers.co.uk/forums/showthread.php?t=43921
http://support.microsoft.com/kb/824255
But as microsoft does not seem to give support for it anymore http://support.microsoft.com/kb/297381 This problem will remain.
So as I am distributing a front end (a folder which contains the front end mde and other files) I thought I could simply include these two OCX files in there and all would be good. It seems that this allows my program to start (normally it does not even start) but as soon as you call the form which contains the control it says that the control is missing. (I am assuming this is because it is not registered in this folder)
As far as I can work out I do not have an option of late binding.
Up until now I have done the most written solution which is go to the problem computer and copy the OCX's into C:\WINNT\system32 (i have never needed to register it though) but this solution is not a long term one.
No offence but I prefer not to use the datepicker that has been developed here in the forum.
My first question is that such a control seems normal/essential for access surely when microsoft stopped distributing it, they offered something new. Did they? What is it?
If there is no replacement, then I know the problem, I have the OCX files, how should I make sure when a computer starts my program that does not by default have these files, reference them somehow. Should I simply distribute them with my front end and at start up do a file FILECOPY to C:\WINNT\system32 if the file is not there?
Last edited: