Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Compiling Question 1

Status
Not open for further replies.

ChewDoggie

Programmer
Joined
Mar 14, 2005
Messages
604
Location
US
We're trying to compile our VB6 application into an EXE. We have a reference to "Microsoft VBScript Regular Expressions 5.5". The functionality for the regular expressions is fine and everything works as expected. However, when we go to compile the project into an EXE, we get this error message stating, "Cannot find file C:\WINDOWS\system32\VBSCRIPT.DLL\3", which, when you look at the references list, this is the location given for the regular expression reference.

So how is it that I can have the functionality of Regular Expressions, but not have this file when we compile?

Hope that's clear.

ciao for niao!

AMACycle

American Motorcyclist Association
 
The message doesn't say you don't have it, just that it's not where the compiler expects it to be. Have you searched for the file to see where it might actually be?


Tracy Dryden

Meddle not in the affairs of dragons,
For you are crunchy, and good with mustard. [dragon]
 
If you're trying to create a packing using the packing and deployment wizard and getting that message, try ignoring it and going on with the job. I did that and the installation package worked just fine, as did the installed program.


Tracy Dryden

Meddle not in the affairs of dragons,
For you are crunchy, and good with mustard. [dragon]
 
I know this is going to sound like a dumb question, but, here goes:

the path appears to list VBScript.DLL as a FOLDER. BUt that can't be the case, is it? I mean, is the "\3" a parameter being passed into the DLL?

I'm not API knowledgeable, as you can tell.



ciao for niao!

AMACycle

American Motorcyclist Association
 
Yes, vbscript.dll in a file. I've no idea what the /3 part means, but I'd guess it's not important for actually locating the file.

Here's where I found vbscript.dll on my system:

C:\WINDOWS\system32\
C:\WINDOWS\ServicePacKFiles\i386\
C:\WINDOWS\$NtServicePackUninstall$\
C:\Documents and Settings\Tracy\My Documents\Downloads\Software\VB Tools\VB Service Pack 6\

I'd guess from the look of things that I got that file from Service Pack 6, although it may already have been in the system32 directory before I loaded SP6.




Tracy Dryden

Meddle not in the affairs of dragons,
For you are crunchy, and good with mustard. [dragon]
 
my VBScript.DLL is located exactly where it should be. Don't know why this blows up while compiling.

Any additional expertise is greatly appreciated.

Thanks to all!


ciao for niao!

AMACycle

American Motorcyclist Association
 
Here's another thing to check: make sure you have "Microsoft VBScript Regular Expressions 5.5" in your project references, but NOT in your components. I've found the hard way that having a reference in both places causes problems.


Tracy Dryden

Meddle not in the affairs of dragons,
For you are crunchy, and good with mustard. [dragon]
 
Well, C:\WINDOWS\system32\VBSCRIPT.DLL\3 means a file called 3 (no extensions or anything) in the path C:\WINDOWS\system32\VBSCRIPT.DLL\. So, if that's the file it's saying it can't find, then whether or not a file called vbscript.dll exists where it's supposed to might not be relevant.

 
Um, not exactly. It actually represents one of multiple Interfaces that the library provides; in this case, \3 of the class library in VBSCRIPT.DLL is the "Microsoft VBScript Regular Expressions 5.5" interface (\2 is "Microsoft VBScript Regular Expressions 1.0")
 
So, you're saying that those multiple interfaces aren't contained in separate files called simply the interface number, but that Microsoft uses file syntax to internally denote which interface it's looking for?
 
I've had this problem in the past.

You are almost certainly missing a dependency of the vbscript.dll.


Take Care

Matt
If at first you don't succeed, skydiving is not for you.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top