|
-
Jan 5th, 2002, 07:34 PM
#1
Thread Starter
Stuck in the 80s
Custom Control Problem
In my application, I have a control in it that I made. When someone uses the application, it says it requires "control.ocx"
I don't find out why it's asking for it. It isn't references anywhere and the control.ctl is included within my project.
Any ideas?
-
Jan 5th, 2002, 07:54 PM
#2
Lively Member
Yeah ive had this problem loads oftimes, basically its because VB isnt particularly good with User Controls, i usually compile the control to an ocx by starting a new activex control and adding my control, then re-reference it in my project. Its annoying it works fne on your comuter but as soon as you give it to another person it doesnt work. The package a development wizard / Setup Wizard might make it work, dunno never tried, but its a possibility.
Groovydaz.
-
Jan 5th, 2002, 07:57 PM
#3
Thread Starter
Stuck in the 80s
I just realized what I said doesn't really describe my problem.
I have a user control (a .ctl) file in my application, and I use it in my program (rather than compiling to an ocx). However, when I send the program to someone else, it says it requires control.ocx. It shouldn't say this because the control is included within my program in an uncompiled form.
I don't really know how to describe this problem very well.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|