Functions not working in XP
 

I have a Microsoft Excel application which uses API calls to open the
dialog box to select a file. For some reason when this API is run in
XP it doesn't work. Now, simple functions like String(x,y) and CurDir
no longer work.

Does anyone know how to fix this?

Thanks!
JJ

Functions not working in XP
 

Sounds like you have a missing reference.
Look under Tools, References and see if any are missing.

RBS


"JJ" wrote in message
oups.com...
I have a Microsoft Excel application which uses API calls to open the
dialog box to select a file. For some reason when this API is run in
XP it doesn't work. Now, simple functions like String(x,y) and CurDir
no longer work.

Does anyone know how to fix this?

Thanks!
JJ

Functions not working in XP
 

Make sure any necessary references has been checked
--
Gary''s Student
gsnu200711


"JJ" wrote:

I have a Microsoft Excel application which uses API calls to open the
dialog box to select a file. For some reason when this API is run in
XP it doesn't work. Now, simple functions like String(x,y) and CurDir
no longer work.

Does anyone know how to fix this?

Thanks!
JJ

Functions not working in XP
 

On my computer, I have Office 2002 SP3 and I have no problems. On the
computer that is having problems, it is running Office 2003 SP2.

I checked the references on the computer where the functions did not
work. The only difference is that it had references to the "Microsoft
Excel 11.0 Object Library" and the "Microsoft Office 11.0 Object
Library", where my computer had references to the "Microsoft Excel
10.0 Object Library" and "Microsoft Office 10.0 Object Library",
respectively.

Usually, this would show as a "MISSING:" reference, but it seemed to
find the references fine. Is there a difference between the two
versions where simple functions like String(x,y) and CurDir would no
longer work?

On Mar 19, 4:32 pm, Gary''s Student
wrote:
Make sure any necessary references has been checked
--
Gary''s Student
gsnu200711

"JJ" wrote:
I have a Microsoft Excel application which uses API calls to open the
dialog box to select a file. For some reason when this API is run in
XP it doesn't work. Now, simple functions like String(x,y) and CurDir
no longer work.

Does anyone know how to fix this?

Thanks!
JJ

Functions not working in XP
 

This is a pretty common problem and the missing reference is the usual cause.

I'd suggest that you go back once more to the offending pc and look for
missing. I'm guessing that you didn't notice it the first time.

JJ wrote:

On my computer, I have Office 2002 SP3 and I have no problems. On the
computer that is having problems, it is running Office 2003 SP2.

I checked the references on the computer where the functions did not
work. The only difference is that it had references to the "Microsoft
Excel 11.0 Object Library" and the "Microsoft Office 11.0 Object
Library", where my computer had references to the "Microsoft Excel
10.0 Object Library" and "Microsoft Office 10.0 Object Library",
respectively.

Usually, this would show as a "MISSING:" reference, but it seemed to
find the references fine. Is there a difference between the two
versions where simple functions like String(x,y) and CurDir would no
longer work?

On Mar 19, 4:32 pm, Gary''s Student
wrote:
Make sure any necessary references has been checked
--
Gary''s Student
gsnu200711

"JJ" wrote:
I have a Microsoft Excel application which uses API calls to open the
dialog box to select a file. For some reason when this API is run in
XP it doesn't work. Now, simple functions like String(x,y) and CurDir
no longer work.

Does anyone know how to fix this?

Thanks!
JJ

--

Dave Peterson

Functions not working in XP
 

I scrolled through the entire list of references and none were
identified as missing. Any other ideas? Is it possible that the Office/
Excel 11.0 OLB files no longer support the same functions that were in
the Office/Excel 10.0 OLB files? I would think that the CurDir
function is one that is used often enough that it would be supported
regardless of the version. Could this problem be related to any of the
common dialog DLLs?

On Mar 19, 5:16 pm, Dave Peterson wrote:
This is a pretty common problem and the missing reference is the usual cause.

I'd suggest that you go back once more to the offending pc and look for
missing. I'm guessing that you didn't notice it the first time.



JJ wrote:

On my computer, I have Office 2002 SP3 and I have no problems. On the
computer that is having problems, it is running Office 2003 SP2.

I checked the references on the computer where the functions did not
work. The only difference is that it had references to the "Microsoft
Excel 11.0 Object Library" and the "Microsoft Office 11.0 Object
Library", where my computer had references to the "Microsoft Excel
10.0 Object Library" and "Microsoft Office 10.0 Object Library",
respectively.

Usually, this would show as a "MISSING:" reference, but it seemed to
find the references fine. Is there a difference between the two
versions where simple functions like String(x,y) and CurDir would no
longer work?

On Mar 19, 4:32 pm, Gary''s Student
wrote:
Make sure any necessary references has been checked
--
Gary''s Student
gsnu200711

"JJ" wrote:
I have a Microsoft Excel application which uses API calls to open the
dialog box to select a file. For some reason when this API is run in
XP it doesn't work. Now, simple functions like String(x,y) and CurDir
no longer work.

Does anyone know how to fix this?

Thanks!
JJ

--

Dave Peterson

Functions not working in XP
 

Does this mean you went back and looked again? Either way, I'd still one more
trip back to that dialog box. There are lots of possible references and it's
easy to scroll by it.

I don't have any other suggestion.

JJ wrote:

I scrolled through the entire list of references and none were
identified as missing. Any other ideas? Is it possible that the Office/
Excel 11.0 OLB files no longer support the same functions that were in
the Office/Excel 10.0 OLB files? I would think that the CurDir
function is one that is used often enough that it would be supported
regardless of the version. Could this problem be related to any of the
common dialog DLLs?

On Mar 19, 5:16 pm, Dave Peterson wrote:
This is a pretty common problem and the missing reference is the usual cause.

I'd suggest that you go back once more to the offending pc and look for
missing. I'm guessing that you didn't notice it the first time.



JJ wrote:

On my computer, I have Office 2002 SP3 and I have no problems. On the
computer that is having problems, it is running Office 2003 SP2.

I checked the references on the computer where the functions did not
work. The only difference is that it had references to the "Microsoft
Excel 11.0 Object Library" and the "Microsoft Office 11.0 Object
Library", where my computer had references to the "Microsoft Excel
10.0 Object Library" and "Microsoft Office 10.0 Object Library",
respectively.

Usually, this would show as a "MISSING:" reference, but it seemed to
find the references fine. Is there a difference between the two
versions where simple functions like String(x,y) and CurDir would no
longer work?

On Mar 19, 4:32 pm, Gary''s Student
wrote:
Make sure any necessary references has been checked
--
Gary''s Student
gsnu200711

"JJ" wrote:
I have a Microsoft Excel application which uses API calls to open the
dialog box to select a file. For some reason when this API is run in
XP it doesn't work. Now, simple functions like String(x,y) and CurDir
no longer work.

Does anyone know how to fix this?

Thanks!
JJ

--

Dave Peterson

--

Dave Peterson

Functions not working in XP
 

If the code works when you precede those calls with VBA:
VBA.CurDir

then it is most probably a missing reference.

NickHK

"JJ" wrote in message
oups.com...
I scrolled through the entire list of references and none were
identified as missing. Any other ideas? Is it possible that the Office/
Excel 11.0 OLB files no longer support the same functions that were in
the Office/Excel 10.0 OLB files? I would think that the CurDir
function is one that is used often enough that it would be supported
regardless of the version. Could this problem be related to any of the
common dialog DLLs?

On Mar 19, 5:16 pm, Dave Peterson wrote:
This is a pretty common problem and the missing reference is the usual
cause.

I'd suggest that you go back once more to the offending pc and look for
missing. I'm guessing that you didn't notice it the first time.



JJ wrote:

On my computer, I have Office 2002 SP3 and I have no problems. On the
computer that is having problems, it is running Office 2003 SP2.

I checked the references on the computer where the functions did not
work. The only difference is that it had references to the "Microsoft
Excel 11.0 Object Library" and the "Microsoft Office 11.0 Object
Library", where my computer had references to the "Microsoft Excel
10.0 Object Library" and "Microsoft Office 10.0 Object Library",
respectively.

Usually, this would show as a "MISSING:" reference, but it seemed to
find the references fine. Is there a difference between the two
versions where simple functions like String(x,y) and CurDir would no
longer work?

On Mar 19, 4:32 pm, Gary''s Student
wrote:
Make sure any necessary references has been checked
--
Gary''s Student
gsnu200711

"JJ" wrote:
I have a Microsoft Excel application which uses API calls to open
the
dialog box to select a file. For some reason when this API is run
in
XP it doesn't work. Now, simple functions like String(x,y) and
CurDir
no longer work.

Does anyone know how to fix this?

Thanks!
JJ

--

Dave Peterson

Functions not working in XP
 

I would think that the CurDir function is one that is used often enough
that it would be supported regardless of the version

When there is a missing reference or in general a problem to do with
references then
the function it points to (not working as you put it) often has no relation
with the
faulty/missing reference. I find if often points to the left function.
I think the compiler points to the first one it comes across.

RBS


"JJ" wrote in message
oups.com...
I scrolled through the entire list of references and none were
identified as missing. Any other ideas? Is it possible that the Office/
Excel 11.0 OLB files no longer support the same functions that were in
the Office/Excel 10.0 OLB files? I would think that the CurDir
function is one that is used often enough that it would be supported
regardless of the version. Could this problem be related to any of the
common dialog DLLs?

On Mar 19, 5:16 pm, Dave Peterson wrote:
This is a pretty common problem and the missing reference is the usual
cause.

I'd suggest that you go back once more to the offending pc and look for
missing. I'm guessing that you didn't notice it the first time.



JJ wrote:

On my computer, I have Office 2002 SP3 and I have no problems. On the
computer that is having problems, it is running Office 2003 SP2.

I checked the references on the computer where the functions did not
work. The only difference is that it had references to the "Microsoft
Excel 11.0 Object Library" and the "Microsoft Office 11.0 Object
Library", where my computer had references to the "Microsoft Excel
10.0 Object Library" and "Microsoft Office 10.0 Object Library",
respectively.

Usually, this would show as a "MISSING:" reference, but it seemed to
find the references fine. Is there a difference between the two
versions where simple functions like String(x,y) and CurDir would no
longer work?

On Mar 19, 4:32 pm, Gary''s Student
wrote:
Make sure any necessary references has been checked
--
Gary''s Student
gsnu200711

"JJ" wrote:
I have a Microsoft Excel application which uses API calls to open
the
dialog box to select a file. For some reason when this API is run
in
XP it doesn't work. Now, simple functions like String(x,y) and
CurDir
no longer work.

Does anyone know how to fix this?

Thanks!
JJ

--

Dave Peterson