There aren't a lot of people who've done any programming in Publisher. It
may take a while for your question to get answered - if at all.

Signature
JoAnn Paules
MVP Microsoft [Publisher]
JoAnn,
Thanks. This would almost seem to be an issue with the VB that is
included in Publisher. As a programmer, I have never seen code act
differently between the step through mode and the full-speed mode.
I know that ofhter programming areas of the MSDN would probably earn me
a flaming for posting in the wrong forum.
The code is designed to change a specific item (the phone number) on
multiple pages of my document (each page is a different flier) for easy
custimization.
Regards,
TexErnie1
> There aren't a lot of people who've done any programming in Publisher. It
> may take a while for your question to get answered - if at all.
[quoted text clipped - 84 lines]
> >>
> >> End Sub
JoAnn Paules [MSFT MVP] - 16 Nov 2005 01:54 GMT
I honestly don't know. I took one entry level class in programming and I
learned that I really suck at it. I'm glad I have many other skills that I
can use to earn a living. :-)

Signature
JoAnn Paules
MVP Microsoft [Publisher]
> JoAnn,
>
[quoted text clipped - 108 lines]
>> >>
>> >> End Sub
Ed Bennett - 16 Nov 2005 08:33 GMT
> Thanks. This would almost seem to be an issue with the VB that is
> included in Publisher. As a programmer, I have never seen code act
> differently between the step through mode and the full-speed mode.
I have observed that when programming Publisher with .NET, some statements
are skipped when running in Release (full-speed) mode but not when running
with a debugger attached.
I have never observed this when not using the PIAs, though, so I assumed it
was an issue with the PIAs.
Looking through some technical articles, I find that the way I've always
worked with VB forms is not the way you're supposed to work with UserForms.
The UserForm is a template, you need to create a specific instance when you
call it from code.
e.g.
Dim myForm As New PhoneNumbers
Load myForm
myForm.Show
HTH

Signature
Ed Bennett - MVP Microsoft Publisher
Texernie1 - 16 Nov 2005 13:44 GMT
Ed,
Thanks for the input. Unfortunately, it did not work. I even added a
DoEvents right after the load with no success. New code is below. Results are
identical as before.
Maybe someone has a better idea as to how to chage specific items on the
pages (in my case the text of wordart on 4 pages) at will? I don't want to
have to copy the pages and change the phone number on each page (I have at
least 6 phone numbers) as this expands my document to 24 pages really quick
and makes changing the designs tough.
Regards,
TexErnie1
Sub Change_Number()
Dim myForm As New PhoneNumbers
MsgBox ("I run")
Load myForm
DoEvents
MsgBox ("I run2")
myForm.Show
End Sub
> > Thanks. This would almost seem to be an issue with the VB that is
> > included in Publisher. As a programmer, I have never seen code act
[quoted text clipped - 19 lines]
>
> HTH
Ed Bennett - 16 Nov 2005 14:02 GMT
> Thanks for the input. Unfortunately, it did not work. I even added
> a DoEvents right after the load with no success. New code is below.
> Results are identical as before.
You could try moving the code from the Initialize event to the Load event,
provided you make sure you unload the form after each use.
Why are you populating the ComboBox at runtime anyway?

Signature
Ed Bennett - MVP Microsoft Publisher
Texernie1 - 17 Nov 2005 03:25 GMT
Ed,
Thanks for the input again. I changed the code to the Load event, but
still no luck. It seems that all the code attached to the form itself has
been disabled. When I click the button on the form, it does nothing. I just
don't understand it. I may have to find an alternate way of doing what I am
needing.
I was loading the dropdown at execution time becuase the properties for
the drop down seem to act differently in Publisher than in most Office
programs. It seems that VB in general acts differently in Publisher than in
the rest of the Office Programs.
Regards,
TexErnie1
> > Thanks for the input. Unfortunately, it did not work. I even added
> > a DoEvents right after the load with no success. New code is below.
[quoted text clipped - 4 lines]
>
> Why are you populating the ComboBox at runtime anyway?