Vis Basic/Vis Studio

      • I bought Vis Basic for a class I’m in; it comes with eight CD’s. One is “Actual” Visual Basic, another is a code library. The others, I don’t know. The printed installation instructions tell you to put in the Vis Studio CD first, but it just tells me I don’t have any of the installed components, and I’m ugly, and my computer sucks anyway. The only two that actually load anything are the Vis Basic CD and the Library CD. Do any of the rest of these do anything important? (I note one is expressly for NT, another says something about WIN2000; those two I don’t need) - MC

Unless Microsoft’s packaging has changed substantially since I purchased my copies of VB (and it may well have) …

It sounds like you purchased Microsoft’s “Visual Studio” product rather than just their Visual Basic product. Visual Studio includes Visual Basic, Visual C++, Visual J++, MSDN, and probably other things I’ve totally forgotten about. Your should be able to install VB from that first CD, but if you were able to install it from the VB CD then you should be fine.

As I (dimly) recall the full Visual Studio installation process, first it wanted to upgrade my copy of Internet Explorer (because the MSDN package required it), then it wanted to install MSDN (because the various compilers’ “help” functions required it), and only then would it let me install the actual compilers. Ithink I had to reboot my PC about five times before the installation process was finished. #$^&*!!

Looks like that’s what happened…look at the disks and documentation and see if you see references to Visual FoxPro…if so, then you’ve gotten the entire studio.

And it’s one serious bitch to install. I finally gave up trying to get MSDN installed on my machine, so now I get to play with MicroSoft’s multi-headed monster, with no help files to go by…

You could probably package the whole thing back up (unless you want VC++, VJ, and VFP) and exchange it for the less pricey VB6 (6 is still the latest, right?)

-David

I use the MSDN help files by running it in the CDROM drive. It’s not too slow.

I have installed it by putting in the first disk and selecting the packages I want. IE 4 SP1 or something is required, in order to install the MSDN library - if there is anything that is blowing up and telling you you are ugly its probably this. I’d uninstall IE first and then try to run the installation. It took me a bit of time but I’ve never had any serious trouble installing this (I’ve installed it probably six times on 4 different computers).

(LMAO) So microsoft finally decided to go for the Civil Suit as well? Discrimination against the ugly…

I had to install Visual Studio 6 for 12 computers. It was not very pleasant. Generally you want to install only the most needed components otherwise you run into ‘Not enough memory’ or ‘You need(input random program which you have never heard of before)’.

I believe that VB6.0 is the most recent, but I am not sure. I use VB5.0 - you can manipulate it to do the same as VB6.0, if you have patience (and way too much time on your hands…). Hopefully that will apply to the newest VB whenever it comes out.

./^_/^\

< o | o >
.<_ | _>
…\U/

  • Hmmm, , , ,
  • I’m not angry; VB seems to be working 100%, I’m just curious what all the rest of this crap is for.
      • Just for fun, all the CD titles, in no particular order:
  • Microsoft Visual Basic 6.0 Professional Edition (this works)
  • MSDN Library-Visual Studio 6.0 -2 CD set-(this works, the rest don’t do nuthin’)
  • Microsoft Visual Studio 6.0
  • Windows 2000 Developer’s Readiness Kit
  • Microsoft MSDE for Visual Studio / Developer Training
  • Microsoft Windows NT Service Pack4
  • Microsoft MSDE for Visual Studio
    The printed material is two booklets:
  • Getting Started Setup Guide for Visual Studio 6.0, and
  • Visual Studio Developing for Windows and the Web
    — There’s nothing that refers particularly to Visual Basic. - MC

That does sound like an odd combination of CD’s…

MSDE is MS’s new data engine, replacing JET as the data engine for Access. It if you nice if you are doing any DB or data access development work. Some of the ADO controls work much better with it.

NT SP4 is kinda pointless without NT,
The W2000 readiness may be of use in the future, depending on how into this you get…

Had to install VS twice at work, no real problems in terms of getting it to work, but the reboots are hell.

If you got VB & MSDN running, that’s all you really need unless you want to program in the rest of the languages…

There are no other languages in that package. Visual Studio is the IDE that Visual Basic uses, MSDN is your online documentation (lots of good stuff in there), and the rest are basically support disks.

It sounds like the new release of Microsoft VB6.0 Professional, or maybe the Visual Basic Educational package.

Does anyone have any experience with the latest version of Microsoft Data Access Components (MDAC)? I believe it is version 2.1.1.3711.11 (GA). I want to upgrade the ODBC drivers on a WinNT machine, but I am hearing horror stories that it breaks your ability to have read/write access to dBase files through Access or VB without the BDE (Borland Database Engine).

      • I bought and loaded MSVis C++ today and then inserted the Visual Studio disk again. This time, it did something; it loaded a bunch of . . . something. Under Start/Programs, both VBasic and VisC++ are listed, but not Vis Studio. I will likely get VisJ++ in a few weeks when that class starts; what will happen then? (I feel like a butch version of Lara Croft) Till then, I have a collection of short stories about my socks, if anyone’s interested, , , - MC

Visual Studio is loaded by default when you load any of those other products. When you buy Visual J++, you’ll just see another entry for J++ in your start menu. The install will note that you already have the VS IDE installed, and will just install the language components you need.

I’m a huge fan of Microsofts Visual Studio. I’ve been programming professionally since 1978, and I’ve never had a collection of tools so powerful and easy to use. And considering the power of the whole package, it’s remarkably bug-free. I remember the days when a simple little C compiler that came on one floppy disk could be counted on to have dozens of bugs that could take weeks to work around. Not so with Microsoft’s stuff.

There ARE reasons why Microsoft is so dominant, and the stability and overall quality of their products is one of them. I work in a large computing/automation engineering shop, and we have standardized around many of Microsoft’s internal management and code practices, because they are just so damned good.