Annoying User Control (URGENT- PLEASE RESPOND)

[khanjan_a2k]

Yes... So... I am working on this pretty big project and I made a "special" control in it that does the scrolling. The control is actually a User Control. Now the problem I am having is that, if I try to use the same control for more than one forms.... It somehow doesn't work and I am tired of trying to figure out why... So what I did for now was that I created each of the components seperately and created a seperate UserControl for them... However now that it is time for me to compile it and put it together... I tried putting a seperate UserControl for each of the forms that need the control to be present and it still doesn't work... Is there any way to get around this...
Please respond ASAP... the clock is ticking...
I'd really really appreciate the help...

[Merri]

Unfortunatenaly without any code this problem seems to be impossible answer well, but here is a wild guess: there just might be something in the control that makes it only work for the certain form, ie. direct referation into Form1 or whatever the form is called. Instead there should be referation to the control parent form or container (was it UserControl.Extender.Container).

[khanjan_a2k]

Sorry About that....
Ok... I hope you know what a click wheel is... that is the UserControl... I am attaching two components, the main form and the settings form... You can try combining them and if you are able to... then please tell me how you did it... There some parts in the settings form that don't work... because they are yet to be fixed... and... the clickevent of the usercontrol in the main form doesn't work since I cannot put all the forms in the same project without letting this problem occur... Hope it helps

[khanjan_a2k]

Since there are no replies... does this mean that there isn't a solution to this problem...?

[si_the_geek]

Many of us can't open .rar files, so we can't even look at the code, let alone provide a solution.

[Bruce Fox]

I have attached above as a Zip file.

[smUX]

Many of us can't open .rar files, so we can't even look at the code, let alone provide a solution.

Not a good enough answer :-P

*real* geeks use RAR compression because of the 15% better ratio over WinZIP (well, actually, real geeks write their own compression, but you get what I mean :-)) so :-P

[Al42]

Really True(tm) Geeks use 7zip, because it's MUCH tighter compression for these files (~60k). Unfortunately the forum doesn't allow us to upload this superior file type.

[Merri]

Many of us can't open .rar files, so we can't even look at the code, let alone provide a solution.

IZarc rules, it opens pretty much anything compressed you need to open.

[si_the_geek]

That's enough off-topic posts folks... the important point is that many people dont have the required software (often due to network rules at work), so there are fewer people who can help.


Back to the point: Well there are a few files missing (such as modProcedures.bas, etc), but I can see a big problem - the project containing your control is not a control project, so it compiles to an executable file instead of to a control.

When you create a new project you get various options, such as "Standard Exe" (which appears to be what you have) and "ActiveX Control" (which is the one you need).

What I would recommend is creating a new ActiveX Control project, and adding the code files from your existing Settings project. When you compile it you will get an .Ocx file (instead of .Exe), which can then be added (via "Project"->"Components") to the projects that are going to use the control.