Converting an app from v -9 to v -2000

Hi |
I've just converted an Acc. app to v -2000.
When compiling, the references claims that a component
is missing. The component is VB6EXT.OLB which probably
belongs to Visual Studio.
I can however not find a 2000-version.
Question:
Can I use the -97 version as it is, or is there a v-2000 one, or are there components replacing it f.x. VBEExt1.OLB
?

Jan
skybergAsked:
Who is Participating?
 
MacRenaCommented:
Is this running on the same machine as the old 97 program used to be?
If so, then this makes no sence.  I would think that the program would be able to find the library file since it found it when it was in 97.
If this is a different computer, then copy the same file over and register it on the new machine's "Windows/System" (or WINNT/System32 - where ever your System folder is).  If copying the file into the directory doesn't automatically register it (Windows should tell you that it has been registered) then click START/RUN and type the following:
regsvr32 VB6Ext.OLB

I have a Reference in my 2000 installation named "M$ Visual Basic 4.0 Development Environment" that points to my VB 4.0 directory's copy of VBEXT32.OLB.
If the file your 2000 is looking for is called "VB6EXT.OLB", then I think it wants that version, and the 97 version will work.

I don't have experience with that library or how it's used, but another option might be to open References and see what IS available, and change the program's requirements to match that.  Like if there is a control that uses the VB6Ext.OLB library, then delete it and add the comparable control from the 2000 environment.  I'm shooting in the dark here.

Good luck,
Mac
0
 
skybergAuthor Commented:
Hi mr MacRena!
As I said, I about to convert an app from -97 to -2000.
On my own PC I have an app -2000.  Looking into the
reference-list "Microsoft visual basic application extesibility" I see a path down below pointing to the
object in uestion. However, the path is to long to be
fully seen, s? I can't figure out what the objectname is.
If You can see it in Yor system, could You kindly send
me the name ?. If it is an .OLB, it is uneccesary tu
register, if it is a .dll then it might be.

Jan
0
 
skybergAuthor Commented:
Ok.
In some cases the system (References) is *screaming'
for .... Extensibility 6.0.
What it really means, is Extensibility 5.3.

Then it works

Jan
0
 
MacRenaCommented:
Hello skyberg,
I see that you replied on 8/21 - I didn't get an email so I'm sorry I didn't reply at that time.
I'm glad you figured it out. Thanks for the points.  I wish there was a way to keep track of EE questions that we have posted in so we can check back a week later.  Then I would have seen your post.
Mac
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.