Hi

I have written a procedure for formatting some Excel CSV download data which
works fine for almost all users.

However, for one user on their first run in the given Excel session, the
macro stops at the same point as it is is on a break point (there is no
error message). There is no break point shown and the macro will continue to
run properly if {F5} or {F8} is pressed. The error occurs for that one user
on different machines. On the second run, all is fine.

Can anyone shed any light on this?

Thanks

Tim

Maybe check their "break on error" setting in the VBE ?

Tim



"Tim Childs" wrote in message
...
Hi

I have written a procedure for formatting some Excel CSV download data
which
works fine for almost all users.

However, for one user on their first run in the given Excel session, the
macro stops at the same point as it is is on a break point (there is no
error message). There is no break point shown and the macro will continue
to
run properly if {F5} or {F8} is pressed. The error occurs for that one
user
on different machines. On the second run, all is fine.

Can anyone shed any light on this?

Thanks

Tim

Hi

thanks for that

in a Windows XP network environment, is that a user-specific setting or part
of the Project itself?

Also, there is no real error - it just stops and highlights the VB line in
yellow: it's weird!

Thanks

Tim

"Tim" <tim j williams at gmail dot com wrote in message
...
Maybe check their "break on error" setting in the VBE ?

Tim



"Tim Childs" wrote in message
...
Hi

I have written a procedure for formatting some Excel CSV download data
which
works fine for almost all users.

However, for one user on their first run in the given Excel session, the
macro stops at the same point as it is is on a break point (there is no
error message). There is no break point shown and the macro will
continue
to
run properly if {F5} or {F8} is pressed. The error occurs for that one
user
on different machines. On the second run, all is fine.

Can anyone shed any light on this?

Thanks

Tim

"Tim Childs" wrote in message
...
Hi

thanks for that

in a Windows XP network environment, is that a user-specific setting or
part
of the Project itself?


Not absolutely sure, but I think it's at the user level.

Tim




Also, there is no real error - it just stops and highlights the VB line in
yellow: it's weird!

Thanks

Tim

"Tim" <tim j williams at gmail dot com wrote in message
...
Maybe check their "break on error" setting in the VBE ?

Tim



"Tim Childs" wrote in message
...
Hi

I have written a procedure for formatting some Excel CSV download data
which
works fine for almost all users.

However, for one user on their first run in the given Excel session,
the
macro stops at the same point as it is is on a break point (there is no
error message). There is no break point shown and the macro will
continue
to
run properly if {F5} or {F8} is pressed. The error occurs for that one
user
on different machines. On the second run, all is fine.

Can anyone shed any light on this?

Thanks

Tim

many thanks - Tim

"Tim" <tim j williams at gmail dot com wrote in message
...

"Tim Childs" wrote in message
...
Hi

thanks for that

in a Windows XP network environment, is that a user-specific setting or
part
of the Project itself?


Not absolutely sure, but I think it's at the user level.

Tim




Also, there is no real error - it just stops and highlights the VB line
in
yellow: it's weird!

Thanks

Tim

"Tim" <tim j williams at gmail dot com wrote in message
...
Maybe check their "break on error" setting in the VBE ?

Tim



"Tim Childs" wrote in message
...
Hi

I have written a procedure for formatting some Excel CSV download
data
which
works fine for almost all users.

However, for one user on their first run in the given Excel session,
the
macro stops at the same point as it is is on a break point (there is
no
error message). There is no break point shown and the macro will
continue
to
run properly if {F5} or {F8} is pressed. The error occurs for that
one
user
on different machines. On the second run, all is fine.

Can anyone shed any light on this?

Thanks

Tim