MSVBVM60.dll HELP!!

[Trip]

Hello all - looking for a little help here.

I've recently complete a large Excel 2000 vba project (3.5 mb sans data). I
have noticed that many functions that worked in Excel 2000 fall apart in XP.
For example:
buffer = Space(varLength)
the keyword "Space" does not work in XP

So, in my searching of the news groups I've come to realize that I need to
include MSVBVM60.dll in my references. However, when I try to add it (it's
named "Visual Basic For Applications") I get the error "Name conflicts with
existing module, project, or object library". Sure enough there's another
reference also named "Visual Basic For Applications" which points to a newer
version of MSVBVM60. But, when I try to remove this newer reference I get
the error "Can't remove control or reference; in use" and I can't figure out
how to rename either.

(or is it the MS Excel 9.0 and MS Office 9.0 Obj Libraries that I'm
missing??)

So, what the heck am I supposed to do to make these basic functions work
(other then debugging all 3.5 mb of code line-by-line)?

Also, does anybody know how I can get the mmcontrol1 reference in there too?
I don't see this any longer either.

Thanks in advance!

Trip

 

[Tom Ogilvy]

It sounds like you have misdiagnosed your problem. Developing in excel 2000
should be no problem for the situation you describe. When opened in
xl2002, the newer version of the Visual basic file will be used and should
not cause the problem you describe. What will cause that problem is some
other reference you have that is not being found in the other computer. You
can see which is causing the problem by going into tools=>Reference (in the
computer with a problem) and you should see one or more References shown as
MISSING. Any reference shown as missing will cause this type of problem
even though "space" is not related to that reference.

For a reference to work, the source file must be on the computer and
registered.

 

[Trip Ives]

Thanks Tom! Your suggestion worked great!

It sounds like you have misdiagnosed your problem. Developing in excel 2000
should be no problem for the situation you describe. When opened in
xl2002, the newer version of the Visual basic file will be used and should
not cause the problem you describe. What will cause that problem is some
other reference you have that is not being found in the other computer. You
can see which is causing the problem by going into tools=>Reference (in the
computer with a problem) and you should see one or more References shown as
MISSING. Any reference shown as missing will cause this type of problem
even though "space" is not related to that reference.

For a reference to work, the source file must be on the computer and
registered.