Calendar control issue KMP 14.11.2005 22:48:02 I have a calendar control in Access 2002 applications that works fine. When we ported all the Access 2002 applications to 2003, the calendar control stopped working at most of the places where it is called. I checked for missing references and the version numbers too – they all seem to be correct. The control works sometimes which surprises me. Also, when our setup application loads the MDEs on production servers, the problem seems to come up. But when each application is individually loaded on a production server, the problem does not come up. The only difference between the Access 2002 and 2003 versions are that the 2003 version applications have been digitally signed. I am wondering if that has anything to do with this issue. If that is the case, then why does it work at some places? Any help will be appreciated. Please let me know if you need more information. Thanks.

Re: Calendar control issue "Douglas J. Steele" <NOSPAM_djsteele[ at ]NOSPAM_canada.com> 14.11.2005 23:29:40 While admittedly a bit of work to retrofit, do yourself a favour and scrap the calendar control and use the all-API approach Stephen Lebans has at http://www.lebans.com/monthcalendar.htm -- Doug Steele, Microsoft Access MVP http://I.Am/DougSteele (no e-mails, please!) "KMP" <KMP[ at ]discussions.microsoft.com> wrote in message news:B803B3E5-73D9-498C-90A0-B421EDC3639C[ at ]microsoft.com... [Quoted Text] >I have a calendar control in Access 2002 applications that works fine. When > we ported all the Access 2002 applications to 2003, the calendar control > stopped working at most of the places where it is called. I checked for > missing references and the version numbers too - they all seem to be > correct. > The control works sometimes which surprises me. > > Also, when our setup application loads the MDEs on production servers, the > problem seems to come up. But when each application is individually loaded > on > a production server, the problem does not come up. > > The only difference between the Access 2002 and 2003 versions are that the > 2003 version applications have been digitally signed. I am wondering if > that > has anything to do with this issue. If that is the case, then why does it > work at some places? > > Any help will be appreciated. Please let me know if you need more > information. Thanks. >

Re: Calendar control issue KMP 15.11.2005 15:06:04 Thanks for your prompt reply. I know this is one of the available options - but is there any way I can get the current calendar control to work. My problem with using a third party control/code is that I will have to keep checking for updates and I am not sure about the kind of support I will get. Please enlighten me if these are some things that don't need attention. Thank you. "Douglas J. Steele" wrote: [Quoted Text] > While admittedly a bit of work to retrofit, do yourself a favour and scrap > the calendar control and use the all-API approach Stephen Lebans has at > http://www.lebans.com/monthcalendar.htm > > -- > Doug Steele, Microsoft Access MVP > http://I.Am/DougSteele > (no e-mails, please!) > > > > "KMP" <KMP[ at ]discussions.microsoft.com> wrote in message > news:B803B3E5-73D9-498C-90A0-B421EDC3639C[ at ]microsoft.com... > >I have a calendar control in Access 2002 applications that works fine. When > > we ported all the Access 2002 applications to 2003, the calendar control > > stopped working at most of the places where it is called. I checked for > > missing references and the version numbers too - they all seem to be > > correct. > > The control works sometimes which surprises me. > > > > Also, when our setup application loads the MDEs on production servers, the > > problem seems to come up. But when each application is individually loaded > > on > > a production server, the problem does not come up. > > > > The only difference between the Access 2002 and 2003 versions are that the > > 2003 version applications have been digitally signed. I am wondering if > > that > > has anything to do with this issue. If that is the case, then why does it > > work at some places? > > > > Any help will be appreciated. Please let me know if you need more > > information. Thanks. > > > > >

Re: Calendar control issue "Ron Weiner" <weinNoSpam1[ at ]mindspring.com> 15.11.2005 15:45:48 If you are after a simple popup calendar that inserts a selected date into a field on you form I recommend that you look here. http://allenbrowne.com/ser-51.html. This is a 100% all Access solution that lives inside your database that you have FULL control over. There are no references, activeX, dll, or com components to worry about. Any computer that can run your database will run the calendar. -- Ron W www.WorksRite.com "KMP" <KMP[ at ]discussions.microsoft.com> wrote in message news:770C97D8-C5F3-46F6-83F8-A64F2A659F3F[ at ]microsoft.com... [Quoted Text] > Thanks for your prompt reply. > I know this is one of the available options - but is there any way I can get > the current calendar control to work. My problem with using a third party > control/code is that I will have to keep checking for updates and I am not > sure about the kind of support I will get. Please enlighten me if these are > some things that don't need attention. Thank you. > > "Douglas J. Steele" wrote: > > > While admittedly a bit of work to retrofit, do yourself a favour and scrap > > the calendar control and use the all-API approach Stephen Lebans has at > > http://www.lebans.com/monthcalendar.htm > > > > -- > > Doug Steele, Microsoft Access MVP > > http://I.Am/DougSteele > > (no e-mails, please!) > > > > > > > > "KMP" <KMP[ at ]discussions.microsoft.com> wrote in message > > news:B803B3E5-73D9-498C-90A0-B421EDC3639C[ at ]microsoft.com... > > >I have a calendar control in Access 2002 applications that works fine. When > > > we ported all the Access 2002 applications to 2003, the calendar control > > > stopped working at most of the places where it is called. I checked for > > > missing references and the version numbers too - they all seem to be > > > correct. > > > The control works sometimes which surprises me. > > > > > > Also, when our setup application loads the MDEs on production servers, the > > > problem seems to come up. But when each application is individually loaded > > > on > > > a production server, the problem does not come up. > > > > > > The only difference between the Access 2002 and 2003 versions are that the > > > 2003 version applications have been digitally signed. I am wondering if > > > that > > > has anything to do with this issue. If that is the case, then why does it > > > work at some places? > > > > > > Any help will be appreciated. Please let me know if you need more > > > information. Thanks. > > > > > > > > >

Re: Calendar control issue "Alex Dybenko" <alexdyb[ at ]PLEASE.cemi.NO.rssi.SPAM.ru> 15.11.2005 19:58:15 Hi, I use this control - and it works fine in all access versions. when you say "stopped working" - what do you mean - control does not show? one thing you have to check - do not reffer to control in form open event, use only form load event and any other, which fires later -- Alex Dybenko (MVP) http://alexdyb.blogspot.com http://www.PointLtd.com "KMP" <KMP[ at ]discussions.microsoft.com> wrote in message news:770C97D8-C5F3-46F6-83F8-A64F2A659F3F[ at ]microsoft.com... [Quoted Text] > Thanks for your prompt reply. > I know this is one of the available options - but is there any way I can > get > the current calendar control to work. My problem with using a third party > control/code is that I will have to keep checking for updates and I am not > sure about the kind of support I will get. Please enlighten me if these > are > some things that don't need attention. Thank you. > > "Douglas J. Steele" wrote: > >> While admittedly a bit of work to retrofit, do yourself a favour and >> scrap >> the calendar control and use the all-API approach Stephen Lebans has at >> http://www.lebans.com/monthcalendar.htm >> >> -- >> Doug Steele, Microsoft Access MVP >> http://I.Am/DougSteele >> (no e-mails, please!) >> >> >> >> "KMP" <KMP[ at ]discussions.microsoft.com> wrote in message >> news:B803B3E5-73D9-498C-90A0-B421EDC3639C[ at ]microsoft.com... >> >I have a calendar control in Access 2002 applications that works fine. >> >When >> > we ported all the Access 2002 applications to 2003, the calendar >> > control >> > stopped working at most of the places where it is called. I checked for >> > missing references and the version numbers too - they all seem to be >> > correct. >> > The control works sometimes which surprises me. >> > >> > Also, when our setup application loads the MDEs on production servers, >> > the >> > problem seems to come up. But when each application is individually >> > loaded >> > on >> > a production server, the problem does not come up. >> > >> > The only difference between the Access 2002 and 2003 versions are that >> > the >> > 2003 version applications have been digitally signed. I am wondering if >> > that >> > has anything to do with this issue. If that is the case, then why does >> > it >> > work at some places? >> > >> > Any help will be appreciated. Please let me know if you need more >> > information. Thanks. >> > >> >> >>

Re: Calendar control issue "Douglas J. Steele" <NOSPAM_djsteele[ at ]NOSPAM_canada.com> 15.11.2005 22:12:49 It's not a third party control: it's built into Windows. That's what APIs are all about. All OCX controls are are wrappers around the APIs. However, due to how OCXs are built, they're prone to versioning problems. Calling the APIs yourself can minimize such problems. -- Doug Steele, Microsoft Access MVP http://I.Am/DougSteele (no e-mails, please!) "KMP" <KMP[ at ]discussions.microsoft.com> wrote in message news:770C97D8-C5F3-46F6-83F8-A64F2A659F3F[ at ]microsoft.com... [Quoted Text] > Thanks for your prompt reply. > I know this is one of the available options - but is there any way I can > get > the current calendar control to work. My problem with using a third party > control/code is that I will have to keep checking for updates and I am not > sure about the kind of support I will get. Please enlighten me if these > are > some things that don't need attention. Thank you. > > "Douglas J. Steele" wrote: > >> While admittedly a bit of work to retrofit, do yourself a favour and >> scrap >> the calendar control and use the all-API approach Stephen Lebans has at >> http://www.lebans.com/monthcalendar.htm >> >> -- >> Doug Steele, Microsoft Access MVP >> http://I.Am/DougSteele >> (no e-mails, please!) >> >> >> >> "KMP" <KMP[ at ]discussions.microsoft.com> wrote in message >> news:B803B3E5-73D9-498C-90A0-B421EDC3639C[ at ]microsoft.com... >> >I have a calendar control in Access 2002 applications that works fine. >> >When >> > we ported all the Access 2002 applications to 2003, the calendar >> > control >> > stopped working at most of the places where it is called. I checked for >> > missing references and the version numbers too - they all seem to be >> > correct. >> > The control works sometimes which surprises me. >> > >> > Also, when our setup application loads the MDEs on production servers, >> > the >> > problem seems to come up. But when each application is individually >> > loaded >> > on >> > a production server, the problem does not come up. >> > >> > The only difference between the Access 2002 and 2003 versions are that >> > the >> > 2003 version applications have been digitally signed. I am wondering if >> > that >> > has anything to do with this issue. If that is the case, then why does >> > it >> > work at some places? >> > >> > Any help will be appreciated. Please let me know if you need more >> > information. Thanks. >> > >> >> >>

Re: Calendar control issue KMP 15.11.2005 23:25:04 Thank you all for helping me out. I am trying to fix this issue and will try all the suggestions. Thanks once again. "Douglas J. Steele" wrote: [Quoted Text] > It's not a third party control: it's built into Windows. That's what APIs > are all about. > > All OCX controls are are wrappers around the APIs. However, due to how OCXs > are built, they're prone to versioning problems. Calling the APIs yourself > can minimize such problems. > > -- > Doug Steele, Microsoft Access MVP > http://I.Am/DougSteele > (no e-mails, please!) > > > > "KMP" <KMP[ at ]discussions.microsoft.com> wrote in message > news:770C97D8-C5F3-46F6-83F8-A64F2A659F3F[ at ]microsoft.com... > > Thanks for your prompt reply. > > I know this is one of the available options - but is there any way I can > > get > > the current calendar control to work. My problem with using a third party > > control/code is that I will have to keep checking for updates and I am not > > sure about the kind of support I will get. Please enlighten me if these > > are > > some things that don't need attention. Thank you. > > > > "Douglas J. Steele" wrote: > > > >> While admittedly a bit of work to retrofit, do yourself a favour and > >> scrap > >> the calendar control and use the all-API approach Stephen Lebans has at > >> http://www.lebans.com/monthcalendar.htm > >> > >> -- > >> Doug Steele, Microsoft Access MVP > >> http://I.Am/DougSteele > >> (no e-mails, please!) > >> > >> > >> > >> "KMP" <KMP[ at ]discussions.microsoft.com> wrote in message > >> news:B803B3E5-73D9-498C-90A0-B421EDC3639C[ at ]microsoft.com... > >> >I have a calendar control in Access 2002 applications that works fine. > >> >When > >> > we ported all the Access 2002 applications to 2003, the calendar > >> > control > >> > stopped working at most of the places where it is called. I checked for > >> > missing references and the version numbers too - they all seem to be > >> > correct. > >> > The control works sometimes which surprises me. > >> > > >> > Also, when our setup application loads the MDEs on production servers, > >> > the > >> > problem seems to come up. But when each application is individually > >> > loaded > >> > on > >> > a production server, the problem does not come up. > >> > > >> > The only difference between the Access 2002 and 2003 versions are that > >> > the > >> > 2003 version applications have been digitally signed. I am wondering if > >> > that > >> > has anything to do with this issue. If that is the case, then why does > >> > it > >> > work at some places? > >> > > >> > Any help will be appreciated. Please let me know if you need more > >> > information. Thanks. > >> > > >> > >> > >> > > >