vbOkCancel
- Thread starter JonyBravo
- Start date
Bob, not to step on any toes here, but you could also find a replacement activeX control to use instead of the default button.
Okay this might get me into some trouble as I have no idea on posting links but anyways
www.planetsourcecode.com has a number of activex controls freely available for download, one of which may resolve JB's question. Please note this in no way implies this site or myself are reponsable for the quality of ActiveX you may download. Use at own risk, it's open source.
boblarson
Smeghead
- Local time
- Today, 02:44
- Joined
- Jan 12, 2001
- Messages
- 32,059
You aren't stepping on toes, but in my experience I would caution anyone AGAINST using ActiveX controls if at all possible. The reason being is that you will need to make sure that each user's machine then has that control installed on their machine and the referencing issues that arise due to users either not having it, or it being registered from a different file location, just isn't worth the hassle unless you absolutely have to have it to get it done. I did have to use an Internet Control for one of my recent programs and I wound up having to create a VB6 installation routine to install the ActiveX control so that we could make sure that the users had the appropriate control.
So, I will generally say to avoid ActiveX controls and go with API programming instead, if that is available. And, if it means creating my own form, or using an ActiveX control, I will go for creating my own form any day over using the control as I can build the form in a matter of minutes and then I am guaranteed to have no MISSING Reference issues with any of my users and don't have to deal with the whole hassle if those missing references were to rear their ugly heads.
Good points Bob 
Generally I only ever create ActiveX if I really really need something outside of the box, as surprisingly VB can do most things. Of course, as you say, this opens a Pandoras box in terms of dll hell etc.
Did a combined project over the net with developers in three separate countries, we spent more time ensuring everyone was on the same ActiveX versions than actually writing code
Generally I only ever create ActiveX if I really really need something outside of the box, as surprisingly VB can do most things. Of course, as you say, this opens a Pandoras box in terms of dll hell etc.
Did a combined project over the net with developers in three separate countries, we spent more time ensuring everyone was on the same ActiveX versions than actually writing code
