Userform problems in VBA-IDE

Userform problems in VBA-IDE

fxcastil
Advocate Advocate
343 Views
3 Replies
Message 1 of 4

Userform problems in VBA-IDE

fxcastil
Advocate
Advocate
I am having problems with Userfoms inside the VBA-IDE environment. If I add a control to the userform it is visible on the form but if I double click on the control it does not start a
click subroutine. Also if I go to the code window for the userform I do not see it in the pull down box which shows all the controls on the userform. I have a program with about 25 small userforms (<20 controls) and two large userforms
(>100 controls). This is causing me many headaches. I have tried rebuilding the project , by exporting each userform and module then importing into a new blank program.

I also have a problem with several copies of the program where it locks up the IDE editor. I can not see any real
differences between these programs.

I have also just created large userform with ten multi-page tabs with a bunch of controls on each page but I can't seem
to duplicate this problem of not recognizing controls as they are added.

Is there a practical size limit to a VBA project ??

If any one has any ideas how to "fix" or debug userforms please help.

The only thing I can think of is to rebuild the large userforms
into smaller userforms. Which will be a slow painful task.


Thanks,

Fred C.
0 Likes
344 Views
3 Replies
Replies (3)
Message 2 of 4

Anonymous
Not applicable
What kinds of controls are you using? Sounds like you browsed out and are
using some of the controls you're not allowed [by MS] to use in a vba
project.

-- Mike
___________________________
Mike Tuersley
___________________________
the trick is to realize that there is no spoon...
0 Likes
Message 3 of 4

fxcastil
Advocate
Advocate
Mike ,

I am using all the "standard" msforms controls (FM20.dll) such as listbox, multipage, tab , command button ,etc. I am also using the Microsoft progress bar control 6.0.

Ok now the "non-standard" controls. I am also using microsoft XP web components "OWC10.dll " which is spreadsheet control provided with Microsoft Office.
This application will be used only on machines running Microsoft Office. As far as I know this control is control
should not be a problem being used on any Office capable
machine.

I am using the freeware thumbnail drawing viewer
" acThumb.ocx "

I know at one time some of these user-forms had a MSflexGrid control, which a programmer with Visual Basic
installed on userforms until we found out we could not use this control on non Visual Basic machines

I have since re-built these user-forms because of problems
we had when different people were creating forms on different machines. I have removed all " non-standard" controls not licensed for VBA.

I was hoping/wishing/dreamiing some knew of a purge/repair
feature for VBA userforms.

Fred C.
0 Likes
Message 4 of 4

Anonymous
Not applicable
Well the progress control is not legal and neither are the Office ones...I
mean ts a fine point and you are right that they should have Office.

The culprit may be the spreadsheet control. These controls are usually not
for vba unless it explicitly states the opposite.

You can also try to Debug>Compile and see what it shakes out. And, then,
you could export all mods/classes/forms to an external location, start a
new project, re-attach all the exported files and see if that cleans things
up any.

-- Mike
___________________________
Mike Tuersley
___________________________
the trick is to realize that there is no spoon...
0 Likes