C
Chrisso
Hi All
I have a utility macro in Word VBA. It has been working for all the
people in my department for a long time now with no problems.
All of a sudden, but only on some people's PCs, a compile error occurs
when I use the Format function:
MsgBox Format(Date, "dd/mm/yyyy")
I can fix this by qualifying the format call with VBA:
MsgBox VBA.Format(Date, "dd/mm/yyyy")
But I want to understand how this occurred and why only on some
people's PCs? My guess is that a library somewhere was updated by our
central IT department - but I dont know which library?
Does anyone know which library Format() comes from? How do I find this
out?
When I look at Tools>References in VB Editor the path of the "Visual
Basic For Applications" is too long to be viewed - I cannot see a way
to make the full path reveal itself. Argh! I am assuming that the
Format function comes from this reference but I cannot confirm this.
Does anyone know?
Does anyone have any similar experience? I need to know how many other
people will get the same error.
Chrisso
I have a utility macro in Word VBA. It has been working for all the
people in my department for a long time now with no problems.
All of a sudden, but only on some people's PCs, a compile error occurs
when I use the Format function:
MsgBox Format(Date, "dd/mm/yyyy")
I can fix this by qualifying the format call with VBA:
MsgBox VBA.Format(Date, "dd/mm/yyyy")
But I want to understand how this occurred and why only on some
people's PCs? My guess is that a library somewhere was updated by our
central IT department - but I dont know which library?
Does anyone know which library Format() comes from? How do I find this
out?
When I look at Tools>References in VB Editor the path of the "Visual
Basic For Applications" is too long to be viewed - I cannot see a way
to make the full path reveal itself. Argh! I am assuming that the
Format function comes from this reference but I cannot confirm this.
Does anyone know?
Does anyone have any similar experience? I need to know how many other
people will get the same error.
Chrisso