Solved

Calendar Control bombs VB in design mode

Posted on 2004-04-06
4
538 Views
Last Modified: 2008-02-01
I have a Calendar Control in a VB program.  I have not worked on the program in a few weeks.  When I go back into the program in design mode, whenever I click on the calendar control, the program says an error has occured and the program must stop.  Is the control corrupted and causing this error?  It would appear i cannot even delete the calendar control because simply clicking on the control is design mode makes VB drop out of memory.  Whats Up?

0
Comment
Question by:dastaub
4 Comments
 
LVL 1

Assisted Solution

by:pawankesari
pawankesari earned 100 total points
ID: 10772121
Can't help you much.

But as far as deleting of the control is concern you can open vbp (Project file) in notepad and delete the reference of Calender Control and save it, then open it in Visual Basic IDE. VB IDE will give you error but finally load the project.

Save a copy of project before doing that.

0
 
LVL 2

Assisted Solution

by:AnantKuslekar
AnantKuslekar earned 100 total points
ID: 10772238
In continution to Comment from pawankesari,
Open project.vbp in notepad see the reference control.
.i.e. <ThatCalendar>.ocx
and u can register that ocx using regsvr32.
If license expires u can delete that .ocx line in project file and save in note pad
0
 
LVL 5

Accepted Solution

by:
Pi7 earned 300 total points
ID: 10772812
dastaub, I've also experienced a similar problem. I don't know what caused it and and I don't know why my solution worked. Maybe you can try it too.
When you open your project in vb, first open your tool box by clicking on its icon in the Tool bar. Only then should you click on any control. (In moving the mouse to click on the tool box icon don't even pass the mouse over a control)

Any method I used was to first run the program immediately after opening my project. After that I could click on any control at design time

Hopefully, it will work for you too

Regards,
Pi7
0
 

Author Comment

by:dastaub
ID: 12139545
the solution turned out to be uninstalling OfficeXP and installing Office 2000.  The error is documented on the Microsoft
web site. The calendar control is corrupted by the OfficeXP install due to lack of backward compatability.  When OfficeXP was
gone and Office 2000 back, it went back to normal.
0

Featured Post

IT, Stop Being Called Into Every Meeting

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

Join & Write a Comment

Introduction While answering a recent question (http://www.experts-exchange.com/Q_27402310.html) in the VB classic zone, I wrote some VB code in the (Office) VBA environment, rather than fire up my older PC.  I didn't post completely correct code o…
Have you ever wanted to restrict the users input in a textbox to numbers, and while doing that make sure that they can't 'cheat' by pasting in non-numeric text? Of course you can do that with code you write yourself but it's tedious and error-prone …
As developers, we are not limited to the functions provided by the VBA language. In addition, we can call the functions that are part of the Windows operating system. These functions are part of the Windows API (Application Programming Interface). U…
Get people started with the utilization of class modules. Class modules can be a powerful tool in Microsoft Access. They allow you to create self-contained objects that encapsulate functionality. They can easily hide the complexity of a process from…

707 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

22 Experts available now in Live!

Get 1:1 Help Now