Bill Feder
asked on
Common Diolog Box
We recently updated our exchange server to 2008 and also updated our terminal server with new one.
We did a transfer of all data and program files. Everything is running fine with only the usual and minor
problems. We are also using office 2003 but will be going to office 2010.
Like I said everything was running fine until I decided I wanted to change some code within the access 2003
front end. When I opened the form in design mode and went to move and active X object (common dialog Box 6.0)
I receive a message saying "I do not have the proper licenses etc. etc." I did a search and found that Microsoft has been
aware of this issue and provides a fix VB6CLI.exe. You can download this and it will give you VBC6.exe.
When I try and run this I get a message " can not find an instance if Visual Basic". That made sense because I never installed Visual Basic on our machines because I would get the message that the disk is incompatable. I thought this
was because we are running 64 bits. I went back to an older machine, 32 bit, with VB already installed. I got the same message.
I copied my most recent front end back to the old terminal server and was able to use all the active X functions including the common dialog box. I am now not sure were the apply the fix or even sure how to run it. I without any doubt need help.
Thanks
Bill
We did a transfer of all data and program files. Everything is running fine with only the usual and minor
problems. We are also using office 2003 but will be going to office 2010.
Like I said everything was running fine until I decided I wanted to change some code within the access 2003
front end. When I opened the form in design mode and went to move and active X object (common dialog Box 6.0)
I receive a message saying "I do not have the proper licenses etc. etc." I did a search and found that Microsoft has been
aware of this issue and provides a fix VB6CLI.exe. You can download this and it will give you VBC6.exe.
When I try and run this I get a message " can not find an instance if Visual Basic". That made sense because I never installed Visual Basic on our machines because I would get the message that the disk is incompatable. I thought this
was because we are running 64 bits. I went back to an older machine, 32 bit, with VB already installed. I got the same message.
I copied my most recent front end back to the old terminal server and was able to use all the active X functions including the common dialog box. I am now not sure were the apply the fix or even sure how to run it. I without any doubt need help.
Thanks
Bill
Perhaps its time to get rid of the ActiveX control. Which one are you using? If it is the file dialog, you can delete the control and switch to code that calls the API or you can switch to Access' native file dialog. I think it has been around since A2003. If it is the calendar control, just delete it. As long as unbound controls are formatted as Dates, A2007 and on will provide a date picker automatically (unless you turn it off).
ASKER
The control is the "common Dialog 6.0 " and I use it mostly to show printers. We do not use The date picker from Microsoft so I am not sure how deleting it would do any good. The problem is
with over 20 Active X controls and acknowledge by Microsoft. If you do a search on the fix I mentioned, VB6CLI.exe, all of the details are there. I am simply not sure how to run the fix, on what machine and how this even happened.
with over 20 Active X controls and acknowledge by Microsoft. If you do a search on the fix I mentioned, VB6CLI.exe, all of the details are there. I am simply not sure how to run the fix, on what machine and how this even happened.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.