VBRUN300.DLL

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

--

Aspire X-Superalien 500W
Asus P4c800E Deluxe
Intel P-4 800 3.0G 1mb cache
Crucial 2x 512MB DDR400
2x WD 80GB Sata 150 7200rpm 8M
Ati Radeon 9800XT 256MB
Audigy 2ZS
Windows XP , home
afternoon
tried to run a program and got "cannot find vbrun300.dll , so went to
microsoft and d/l it now i dont know what to do with it. think i am
supposed to have microsoft visual basic 3.0, but cannot find it on my pc i
have windows xp home.
help me out if you can.
thanks much
larry
 
vbrun300.dll is used to run programs created in Visual Basic 3.

Depends on what program cannot find vbrun300.dll.

Mine is in C:\Program Files\Microsoft Works

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
 
Wesley said:
vbrun300.dll is used to run programs created in Visual Basic 3.

Depends on what program cannot find vbrun300.dll.

Mine is in C:\Program Files\Microsoft Works
The file goes in the Windows/System file - did you find a copy of the
file? I have it if you need it.
Richard
 
Download and install the latest Visual Basic 6.0 Run-time Files
http://www.microsoft.com/downloads/...24-4122-44af-8ab4-7c039d9bf629&DisplayLang=en

--
Regards,
Bert Kinney MS-MVP Shell/User
http://bertk.mvps.org

larry wrote:

--

Aspire X-Superalien 500W
Asus P4c800E Deluxe
Intel P-4 800 3.0G 1mb cache
Crucial 2x 512MB DDR400
2x WD 80GB Sata 150 7200rpm 8M
Ati Radeon 9800XT 256MB
Audigy 2ZS
Windows XP , home
afternoon tried to run a program and got "cannot find vbrun300.dll , so
went to
microsoft and d/l it now i dont know what to do with it. think i am
supposed to have microsoft visual basic 3.0, but cannot find it on my pc
i
have windows xp home.
help me out if you can.
thanks much
 
WINDOWS\System32 maybe, but I doubt Windows/System. Windows\System is for
old 16-bit stuff.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
 
Make sure that you don't have multiple copies of that on your PC. There
used to be a problem with program "installs" copying visiual basic runtime
libraries to a newly created directory, during program installation, that
would conflict with a "matching filename" one in the \Windows directory,
....or was that the \windows\system directory ? ...can't remember now !

regards, Richard
 
Wesley Vogel said:
WINDOWS\System32 maybe, but I doubt Windows/System. Windows\System is for
old 16-bit stuff.

Which VBRUN300 is (1993).

VB3.0 is/was a 16 bit app.

All its DLL's and VBX's should go in WINDOWS\SYSTEM.
 
You definitely got me on the 16-bit bit. ;-)
All its DLL's and VBX's should go in WINDOWS\SYSTEM.

Not if you do not have VB3.0 and an application such as Microsoft Works
needs vbrun300.dll. Then it should be in the folder that the application
placed it in in the first place. I.e Program Files\Microsoft Works

I assume that Microsoft Works Suite 2004 needs vbrun300.dll or it wouldn't
have installed vbrun300.dll in Program Files\Microsoft Works in the first
place. If I moved it to WINDOWS\SYSTEM, it would break whatever part of
Works that needs vbrun300.dll. Something for backward compatibility maybe.

The OP has not given enough info for anyone to actually answer his question.

I am not sure why I even posted in the first place, I was only guessing,
like everyone that posted.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
 
Wesley Vogel said:
You definitely got me on the 16-bit bit. ;-)


Not if you do not have VB3.0 and an application such as Microsoft Works
needs vbrun300.dll. Then it should be in the folder that the application
placed it in in the first place. I.e Program Files\Microsoft Works

Actually, I think we're both right.

The thinking behind putting it in WINDOWS\SYSTEM is that if
you put it there, you only need one copy for ALL VB 3.0 apps
regardless of where they are - it's shared by all of them. I have written
and run tons of 3.0 apps, residing in different directories,
on only the single copy if it's in this particular location.

Of course what you said is true as well, if it's in the directory
from which the 3.0 app was launched, it'll find it and run. But
ONLY that app.

Remember, hard disks were about 500M max in '93, and you
didn't want to be sprinkling 389 KB (398,416 bytes) .DLL's all
over the place.

Nowadays, it matters not.
 
Back
Top