Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

problem with Command1.visible property in UserControl

Posted on 2001-07-19
12
Medium Priority
?
285 Views
Last Modified: 2008-03-03
Dear friends,
I am having a weird problem, i hope someone can tell me where i am going wrong.
My requirements are one simple usercontrol with a command button and a property "visible" for the command button. My code for the usercontrol are as below:
_________________________________________________

Public Property Get showButton() As Boolean
    showButton = cmdButton.Visible
End Property

Public Property Let showButton(ByVal New_showButton As Boolean)
    cmdButton.Visible() = New_showButton
    PropertyChanged "showButton"
End Property

Private Sub UserControl_ReadProperties(PropBag As PropertyBag)

cmdButton.Visible = PropBag.ReadProperty("showButton", False)
End Sub

Private Sub UserControl_WriteProperties(PropBag As PropertyBag)
Call PropBag.WriteProperty("showButton", cmdButton.Visible, False)
End Sub
_____________________________________________________

The code above works fine, if i have a standalone project with one form and one usercontrol but if i copy and paste this code in one of my usercontrol in the project where i am using visual sourcesafe, it gives me weird results.
In this project, if i put the usercontrol on one of the form and change the "showbutton" property, it works fine if i close and open the form but once i save the project and open it again the property is lost and it changes to false.
Its not that the project is not saved, the changes other than the property are changed.
I am tired of this error. Does anyone have idea about what i am doing wrong......
Any kind of help would be appreciated.
Thanks.

0
Comment
Question by:Hakims
12 Comments
 
LVL 8

Expert Comment

by:Dave_Greene
ID: 6298243
<will look at this a bit later>
0
 
LVL 22

Accepted Solution

by:
CJ_S earned 200 total points
ID: 6298322
You should also use the userControl_InitProperties procedure. The InitProperties is the first one to occur when the control first loads.

regards,
CJ

0
 
LVL 8

Expert Comment

by:DennisBorg
ID: 6298329
Hakims:

I believe you will need to use the InitProperties Event in addition to the ReadProperties and WriteProperties events.

See the VB documentation on creating custom controls for more details.

-Dennis Borg
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 

Author Comment

by:Hakims
ID: 6298435
can you tell me how to use the initproperties?
How will my above code look if i add the initproperties.
Thanks

But why is the control working on standalone project and gives problem with visual sourcesafe project...Any way if you could give me the code for initproperties i would try.
0
 
LVL 22

Expert Comment

by:CJ_S
ID: 6298459
Private Sub UserControl_InitProperties()
    cmdButton.Visible = False
    PropertyChanged "showButton"
End Sub
0
 

Author Comment

by:Hakims
ID: 6298520
i am sorry but this has no effect, still the same problem.
0
 

Author Comment

by:Hakims
ID: 6298554
I found something just now.
I copied the whole of my Project on Visual sourcesafe and made a local copy.
Now this time i do not connect to visual sourcesafe and work with the local copy .. and the same code works fine.
Amazing.. why is it happening like this.
any VISUAL SOURCESAFE experts here..
Am i doing something wrong while checking in the form ... ummm i think no, because i have created other properties too in this control and they are working fine except this visible property.
Still waiting for a solution. :(
0
 

Author Comment

by:Hakims
ID: 6298564
I found something just now.
I copied the whole of my Project on Visual sourcesafe and made a local copy.
Now this time i do not connect to visual sourcesafe and work with the local copy .. and the same code works fine.
Amazing.. why is it happening like this.
any VISUAL SOURCESAFE experts here..
Am i doing something wrong while checking in the form ... ummm i think no, because i have created other properties too in this control and they are working fine except this visible property.
Still waiting for a solution. :(
0
 
LVL 22

Expert Comment

by:CJ_S
ID: 6298576
It might be that an earlier version of the control is in Visual SourceSafe. When you then create a new one, and not update the control in sourcesafe, it might give you that effect since it will try to use that one. This only goes when you are also using the visual component manager.

regards,
CJ
0
 

Author Comment

by:Hakims
ID: 6298668
I am adding this property in an existing control and i am doing the check in also properly.
0
 
LVL 49

Expert Comment

by:DanRollins
ID: 7156219
Hi Hakims,
It appears that you have forgotten this question. I will ask Community Support to close it unless you finalize it within 7 days. I will ask a Community Support Moderator to:

    Accept CJ_S's comment(s) as an answer.

Hakims, if you think your question was not answered at all or if you need help, just post a new comment here; Community Support will help you.  DO NOT accept this comment as an answer.

EXPERTS: If you disagree with that recommendation, please post an explanatory comment.
==========
DanRollins -- EE database cleanup volunteer
0
 
LVL 1

Expert Comment

by:Computer101
ID: 7182281
Comment from expert accepted as answer

Computer101
E-E Moderator
0

Featured Post

Ask an Anonymous Question!

Don't feel intimidated by what you don't know. Ask your question anonymously. It's easy! Learn more and upgrade.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

There are many ways to remove duplicate entries in an SQL or Access database. Most make you temporarily insert an ID field, make a temp table and copy data back and forth, and/or are slow. Here is an easy way in VB6 using ADO to remove duplicate row…
This article describes how to use a set of graphical playing cards to create a Draw Poker game in Excel or VB6.
Get people started with the process of using Access VBA to control Outlook using automation, Microsoft Access can control other applications. An example is the ability to programmatically talk to Microsoft Outlook. Using automation, an Access applic…
This lesson covers basic error handling code in Microsoft Excel using VBA. This is the first lesson in a 3-part series that uses code to loop through an Excel spreadsheet in VBA and then fix errors, taking advantage of error handling code. This l…
Suggested Courses

772 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