I have run into a problem when I code using .Font property. I am using
Excel 2003.

The code can be anything that calls up the font property, like
Cells(1,1).Font.ColorIndex = 3

When Excel runs it the first time, it takes quite a few seconds to
accomplish. However, after that,it runs at speed.

This also happens if I format a cell's font the first time I access the
font property in Excel wihtout using code.

Is there a way to get around this delay? Or is it my copy of Excel?

As I said, once Excel opens up the font property, it calls up the font
in a normal speed after. No more delay.

I appreciate any help on this issue.

Thank you.

Just a complete guess...

Do you use a network printer or a local printer? If you use a network printer,
try changing to a local printer.

In fact, try changing to a different printer if that doesn't work.

Louis wrote:

I have run into a problem when I code using .Font property. I am using
Excel 2003.

The code can be anything that calls up the font property, like
Cells(1,1).Font.ColorIndex = 3

When Excel runs it the first time, it takes quite a few seconds to
accomplish. However, after that,it runs at speed.

This also happens if I format a cell's font the first time I access the
font property in Excel wihtout using code.

Is there a way to get around this delay? Or is it my copy of Excel?

As I said, once Excel opens up the font property, it calls up the font
in a normal speed after. No more delay.

I appreciate any help on this issue.

Thank you.

--

Dave Peterson

Dave Peterson wrote:
Just a complete guess...

Do you use a network printer or a local printer? If you use a network printer,
try changing to a local printer.

In fact, try changing to a different printer if that doesn't work.

Louis wrote:
I have run into a problem when I code using .Font property. I am using
Excel 2003.

The code can be anything that calls up the font property, like
Cells(1,1).Font.ColorIndex = 3

When Excel runs it the first time, it takes quite a few seconds to
accomplish. However, after that,it runs at speed.

This also happens if I format a cell's font the first time I access the
font property in Excel wihtout using code.

Is there a way to get around this delay? Or is it my copy of Excel?

As I said, once Excel opens up the font property, it calls up the font
in a normal speed after. No more delay.

I appreciate any help on this issue.

Thank you.

Thank you for the suggestion. Yes, I use a networked printer in the
office. I tried another user's copy of Excel, and that seemed to be
normal. I will try to switch to another printer and try, but I cannot
permanently do that.

I have coded around the problem - I format a cell when the VBA code
starts, and I print out "Please wait". Then after that, everything is
normal. If the user's copy of Excel does not have that problem, they
wouldn't even see the message.

Thanks.

I'd try reinstalling the printer drivers. Or get updated drivers from the
manufacturer.


Louis wrote:

Dave Peterson wrote:
Just a complete guess...

Do you use a network printer or a local printer? If you use a network printer,
try changing to a local printer.

In fact, try changing to a different printer if that doesn't work.

Louis wrote:
I have run into a problem when I code using .Font property. I am using
Excel 2003.

The code can be anything that calls up the font property, like
Cells(1,1).Font.ColorIndex = 3

When Excel runs it the first time, it takes quite a few seconds to
accomplish. However, after that,it runs at speed.

This also happens if I format a cell's font the first time I access the
font property in Excel wihtout using code.

Is there a way to get around this delay? Or is it my copy of Excel?

As I said, once Excel opens up the font property, it calls up the font
in a normal speed after. No more delay.

I appreciate any help on this issue.

Thank you.

Thank you for the suggestion. Yes, I use a networked printer in the
office. I tried another user's copy of Excel, and that seemed to be
normal. I will try to switch to another printer and try, but I cannot
permanently do that.

I have coded around the problem - I format a cell when the VBA code
starts, and I print out "Please wait". Then after that, everything is
normal. If the user's copy of Excel does not have that problem, they
wouldn't even see the message.

Thanks.

--

Dave Peterson