References Library

Hi Expert,

I have a VB project and in it contains functions/routines like LCase(), UCase, and Mid() which are basic functions that VB should have.  But when I tried to run or compile it, it gives me an error.  So I checked in the References Libraries and found that "MISSING: Microsoft Common Dialog 2.0".  But when I tried on another computer, it works without any Libraries Missing.  Is there a way to fix this problem?  In your opinion, what is the problem by the way?


Thanks a mil!
JB
JamesBingAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

GrahamSkanRetiredCommented:
What is the error?
0
Michael_DCommented:
Check File : C:\{WinDir}\System32\COMDLG32.ocx
Is it exist?
0
GrahamSkanRetiredCommented:
James,
I have seen this problem a couple of times before - none of the string functions work - but it was a long time ago, so any info, such as the Error message,  you could give might remind me.

I think the missing Common Dialog is a red herring.
0
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

avi247Commented:
Whats your VB version and Service Pack?

1. Open up a new project. In Form Load, type Lcase( and check to see if you get Intellisense from VB.
2. Is it giving an error for those functions LCase(), UCase, and Mid() or is it throwing an error somewhere else i.e where common dialog functionality is used. I opened up a new project with default references (Visual Basic for Applications,  Visual Basic runtime objects and procedures, Visual Basic objects and Procedures, OLE Automation) and those string functions work fine.

I would say,
Reinstall VB on that machine, I think either runtime or dependent libraries are corrupt.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Ryan ChongBusiness Systems Analyst , ex-Senior Application EngineerCommented:
You may try use/call common dialog boxes from API instead, which No need to use additional library of M$ Common Dialog control, ya.. then you need to change the code a bit but it will eliminate your MISSING Library problem.

A good example by Ark:
CDlgEx -- Encapsulates Windows Dialog Functions into One Class
http://www.freevbcode.com/ShowCode.Asp?ID=631

Else another suggestion is to ensure that you always includes the M$ Common Dialog Control in your setup package/ installer, so that it will install on target machine and eliminate MISSING Library problem.

regards
0
Erick37Commented:
The string functions you mentioned are in the VBA (visual basic for applications) module.  Add a reference to that, if it is available.
0
Erick37Commented:
BTW, while in the VB IDE, press F2.  This brings up the object browser.  There is a dropdown which lists all references your project is holding.  You can search <all libraries> for Lcase and see what pops up.

Good luck!

P.S.
You said "thanks a mil" Isn't a mil = 0.001?  Shouldn't it be "Thanks a Gig?"  :]]
0
Erick37Commented:
Interesting.

In my References, there are 6 listings for Visual Basic for Applications

c:\windows\system32\msvbvm50.dll
c:\windows\system32\vbaend32.olb
C:\Program Files\Common Files\Microsoft Shared\VBA\VBA6\VBE6.DLL
C:\WINDOWS\System32\VEN2232.OLB
C:\WINDOWS\System32\VBAEN32.OLB

and this one is currently referenced by default (how did it end up in a setup directory?):
C:\Program Files\Microsoft Visual Studio\VB98\proj\DM2000\setup\Support\MSVBVM60.DLL

0
JamesBingAuthor Commented:
Reinstalled, it works!!  I guess I'm missing Microsoft Common Dialog 6.0 (SP3).

Thanks guys
0
Michael_DCommented:
That what I've asked at the very begining of the thread if the file exist. It is very "common" problem. I think you have uninstalled some program recently. COMDLG32.ocx was removed as well. Do you remember what application you had uninstalled the last. I would like to  recreate this situation if possible
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Visual Basic Classic

From novice to tech pro — start learning today.