I have about 12 Visual Basic 6 books. This by far goes into detail into things I normally do in VB than any other of the books I have. This book covers good ground on things such as using the explaining VB's controls and covers ADO better in a quicker time than most books. I still use this book a lot when I am working on legacy stuff. If you are creating standalone applications in VB6 with database activities, this book is a must-have and invaluable.
Everybody seems to have different opinions on programming books, see any book and look at the plethora of different reviewer responses. This book has helped me personally too many times to count. Julia, you Rock!! I have been learning VB6 on and off for about 1 year now.
I am teaching myself via books, I bought the 'Programming in visual basic 6.0' by the same aurthors to start with. That book I found to be excellent, and started me on projects. I decided to buy 'advanced Programming in visual basic 6.0'. This book is also good and easy to follow, however, alot of the content is almost identicle to the first book, I would say 60% of this book is covered in the previous edition.
Download Visual Studio 6.0 Full + MSDN CD 780 Mb via 4 shared.com _ 8 direct links. The website in the video: http://vb6access2003.blogspot.com/201. Jun 26, 2009 Greetings, Firstly, apologies if this topic is out of the scope of this board, but I am stumped. Basically, we have an old Visual Basic 6.0 application which currently accesses an Access database, but which we would like to upgrade to an SQL compact edition database.
Three stars for teaching what I already have been tought by the first book. I have about 12 Visual Basic 6 books. This by far goes into detail into things I normally do in VB than any other of the books I have. This book covers good ground on things such as using the explaining VB's controls and covers ADO better in a quicker time than most books. I still use this book a lot when I am working on legacy stuff. If you are creating standalone applications in VB6 with database activities, this book is a must-have and invaluable.
Everybody seems to have different opinions on programming books, see any book and look at the plethora of different reviewer responses. This book has helped me personally too many times to count.
Julia, you Rock!! I have been learning VB6 on and off for about 1 year now. I am teaching myself via books, I bought the 'Programming in visual basic 6.0' by the same aurthors to start with.
That book I found to be excellent, and started me on projects. I decided to buy 'advanced Programming in visual basic 6.0'. This book is also good and easy to follow, however, alot of the content is almost identicle to the first book, I would say 60% of this book is covered in the previous edition. Three stars for teaching what I already have been tought by the first book. This book may not be perfect, but it's close. I've been teaching with the Bradley & Millspaugh books for 3 years now and was excited about this new one that focuses on database and objects. I like the fact that there is not a lot of fluff included.
Code at the end of every chapter that illustrates chapter concepts is welcome. The book is fine, however I find the instructor resources to be abysmal. For instructors publishers typically provide programs as answers to the programming exercises at the end of the chapters - but the teacher examples for this book are horrid. The database programs won't run at first because the samples don't use the author's advice about using VB's App.Path. At times various forms won't load; again because App.Path isn't used. Instructions say to do a certain thing but the example doesn't implement it.
There are no comments and little indentation in the code examples. In order to use the sample code included for instructors, you have to re-write a lot of it yourself. So, if you want just the book - that's fine. But if you're looking for teacher resources to accompany the text.well. This is actually a really good book. I used this text to learn Advanced VB 6.0 after I learned from the preceeding text, Beginning Programming in Vsual Basic 6.0, and I still use it when writing typical VB app projects.
The book is excellent at showing how various controls are used and manipulated in code as well as visually using the IDE. Makes good examples of a coding techniques, SDI/MDI, control properties, Let-Set-Get, classes, modules, VB OOP, forms, ADO, and reports generation. Also explains ActiveX Components, DHTML, and publishing for distribution.
What I liked most about the authors approach is the that the code is very easy to follow and makes perfect sense. The book also explains using code to control the program instead of relying completely on the RAD aspect of VB, which is easy to do since you can actually write a complete application without writing a single line of code. Unfortunately, some points of interest are difficult to find weeks after completing a chapter, as they are not always documented in the TOC. I also didn't like that each subject or technique being demonstrated adds more functionality to a project started in a previous chapter. This was a relatively minor thing compared to the usefulness of the book. Overall, a very good learning text when used in a classroom the way the author intended.
All of the sample code works and it's code you can actually use-that alone is worth at least 4 stars. I teach Visual Basic Programming, and have read a dozen books on Advanced VB while searching for a new textbook. This book does the best job of both giving good examples and explaining how VB works.
Some books have lots of coding examples, but leave you with little understanding of how to design on your own. This book also has far less errors than any other book I've used. The accompaning CD has programs to go along with every chapter. It's a wonderful book, and the one I'll be using next year! It covers ADO well, and is the best introduction to ASP I've read.I gave it one star because I couldn't give it none.
While I'm only in VB II, I have over 200 hours of college credit and 18 hours of computer science. This is the worst textbook I have ever used. It is filled with errors-ex. 23, used MCSD instead of MSDN, p. 95, 'The key field.may be a text field, such as last name, or a combination, such as last name and first name (I guess this is technically correct, but I sure don't want the authors designing any databases for me), p. 223, program code Sets variables but doesn't declare them first.
The different chapters appear to be written by different authors. Chapter 3 uses a step-by-step tutorial in excruciating detail. None of the other chapters up through 5 use this style.
Chapter 5 doesn't even give program snippets complete enough to see what the authors are trying to do. On the other hand p. 177 gives three examples of a sort procedure, changing only the field name. The authors introduce topics without giving enough detail to determine their significance. They may or may not come back to them in later chapters.
Example, unbound controls on p. Parameterized queries are introduced on p. 185 and not even discussed with the Command object in chapter 5. The coverage of SQL is pathetic, at best. The first 200 pages of the text emphasize the DataControl and the DataEnvironment and then on p. 208 the authors say 'You will find that most professional VB database applications use ADO code except in 'quick and simple' projects.' Then why did we just spend six weeks on them?
I wouldn't waste shipping charges on this book. Surely, there is something better.
Which is kinda sad, really. I mean, at this point, if you lose/damage your October 2001 Help CD's, it'll cost you.what is it, about $1000 for an MSDN subscription?just to get the freakin' help files that go with VB6. I suspect some of the peer-to-peer file sharing services would have ISO images of the CDs available (which is NOT legal in most countries), but of course, you take your chances there, since there could be embedded viruses or who knows what! Rob 'MikeD' wrote in message news:[email protected]. Ken Halter 6/7/2007, 9:40 น.
'Robert Morley' wrote in message news:elxZIp%[email protected]. Which is kinda sad, really. I mean, at this point, if you lose/damage your October 2001 Help CD's, it'll cost you.what is it, about $1000 for an MSDN subscription?just to get the freakin' help files that go with VB6. Microsoft Library Subscription - $199 (not sure if that includes access to the October 2001 version) Visual Studio 2005 Professional Edition with MSDN Professional Subscription ($1,199.00) Visual Studio 2005 Team Suite with MSDN Premium Subscription ($10,939.00). Robert Morley wrote: Which is kinda sad, really. I mean, at this point, if you lose/damage your October 2001 Help CD's, it'll cost you.what is it, about $1000 for an MSDN subscription?just to get the freakin' help files that go with VB6.
Totally agree. These 'obsolete'.documentation. files (is knowledge ever obsolete?) really need to be available to the entire community. I suspect some of the peer-to-peer file sharing services would have ISO images of the CDs available (which is NOT legal in most countries), but of course, you take your chances there, since there could be embedded viruses or who knows what! Used to be an active torrent listed at, yeah. But it seems no one's seeding anymore.NET: It's About Trust!
Robert Morley 6/7/2007, 11:05 น. I just checked eMule, which pulls from the eDonkey network and several others, and there's a file there called MSDNOCT2001.iso, but it's 1.45G. That sounds awfully large for a single CD ISO image. Does the ISO standard support packaging multiple CD's in one file? Anyway, that one's got 16 sources currently, most of whom appear to be mass uploaders, as I started downloading from 6 different people within moments of adding the file.
Noticeably, most of them are in China (where I believe copyright law doesn't apply or at least isn't respected). Anyway, I'm not going to download the file; I have two copies of the MSDN 2001 CDs, so I'm not going to waste my time and one or more CDs on finding out if it's genuine or not.:) If anybody else wants/needs to try, you at least know that it's out there now.or appears to be. Peterson' wrote in message news:uR$Z0y%[email protected].
Ken Halter 6/7/2007, 11:14 น. 'Robert Morley' wrote in message news:%23sDp%[email protected]. I just checked eMule, which pulls from the eDonkey network and several others, and there's a file there called MSDNOCT2001.iso, but it's 1.45G. That sounds awfully large for a single CD ISO image. Does the ISO standard support packaging multiple CD's in one file?. That iso's probably designed to be burned to DVD. Like this one (name snagged from MSDN downloads page) for VS2005 pro envs2005prodvd.iso - ISO-9660 DVD Image (2760 MB) - Ken Halter - MS-MVP-VB - Please keep all discussions in the groups.
In Loving Memory - dpb 6/7/2007, 11:23 น. 'Robert Morley' wrote in message news:%23sDp%[email protected]. I just checked eMule, which pulls from the eDonkey network and several others, and there's a file there called MSDNOCT2001.iso, but it's 1.45G. That sounds awfully large for a single CD ISO image. The old MSDN library used to come on 3 CDs, so the file size sounds right, and as Ken said, it's most likely the DVD ISO, which became an option in the early 00's. Robert Morley 6/7/2007, 12:29 น. Speaking of, is VB documentation no longer online at all at MSDN?
I was away from installation and looking the other day and could find no links to other than the Tips/FAQ/Solutions links, no way to find actual documentation that I could find??? Thanks, somehow I couldn't seem to find at the thime what looks straightforward going backwards up the tree from the link. Who knows what I did wrong then now?:( You started at Microsoft when you should have started at Google.:) Robert Morley 6/7/2007, 14:28 น. Speaking of, is VB documentation no longer online at all at MSDN? I was away from installation and looking the other day and could find no links to other than the Tips/FAQ/Solutions links, no way to find actual documentation that I could find???
Thanks, somehow I couldn't seem to find at the thime what looks straightforward going backwards up the tree from the link. Who knows what I did wrong then now?:( Thanks - This is what I was quoting. From that link I'm taken to a Product Documentation screen, but I don't see any downloads. Then I go up to the MSDN Library link/branch but I don't see any downloads. Then I go to the MSDN Library Archive but it doesn't have anything.
Must be right in front of my face, but I don't see it. Thanks again for your quick response. Sent via Developersdex. dpb 10/7/2007, 13:59 น.
C Rule wrote: Speaking of, is VB documentation no longer online at all at MSDN? I was away from installation and looking the other day and could find no links to other than the Tips/FAQ/Solutions links, no way to find actual documentation that I could find???
Thanks, somehow I couldn't seem to find at the thime what looks straightforward going backwards up the tree from the link. Who knows what I did wrong then now?:( Thanks - This is what I was quoting. From that link I'm taken to a Product Documentation screen, but I don't see any downloads. I wasn't asking about downloads, I had thrown in a sidebar request as I hadn't located VB doc's online in an earlier search. Don't think it is available as download.MS is still trying to find the magic silver bullet or wooden stake to kill the beast entirely but hasn't been able to totally succed.:) - MikeD 10/7/2007, 14:25 น.
'Raj' wrote in message [email protected]. I am lookin to download the vb 6.0 msdn setup file as my cd has got corrupted and the drive is not recognising the cd. Looking back, I know see that you started this whole thread with that very same question. That's why you quote. And changing the name you use to post doesn't make things any easier (assuming you are also posting as 'C Rule' too, which appears to be the case).
As mentioned in the very FIRST reply you got, you can't download this unless you have an MSDN Library subscription. The documentation is available online, but it's not downloadable. If you contact Microsoft, they may be able to send you a replacement disc.
Right off-hand, I don't know exactly how (or who) to contact as MS for replacement discs, but Im sure the information has to be somewhere on their general support site. Also, you should verify it's actually the disc and not your drive that's the problem.
Try using the disc in another drive (friend's computer, work computer, etc.). Unless you're abusing a CD or DVD, they don't normally just 'get' corrupted. Mike Microsoft MVP Visual Basic C Rule 11/7/2007, 7:48 น. Looking back, I know see that you started this whole thread with that very same question. That's why you quote. And changing the name you use to post doesn't make things any easier (assuming you are also posting as 'C Rule' too, which appears to be the case). As mentioned in the very FIRST reply you got, you can't download this unless you have an MSDN Library subscription.
The documentation is available online, but it's not downloadable. If you contact Microsoft, they may be able to send you a replacement disc. Right off-hand, I don't know exactly how (or who) to contact as MS for replacement discs, but Im sure the information has to be somewhere on their general support site.
Also, you should verify it's actually the disc and not your drive that's the problem. Try using the disc in another drive (friend's computer, work computer, etc.). Unless you're abusing a CD or DVD, they don't normally just 'get' corrupted. I'm only posting as C Rule - and I don't have the corrupted CD. I've been assigned to work on a VB 6 app.
I've never worked in VB 6 (only C# NET) so I downloaded VB 6 via my MSDN subscription. When I open the application in VB 6 I'm getting an error and when I clicked on Help, it's telling me that the MSDN collection does not exist and to reinstall MSDN. When I googled that error, I saw it was because I needed to intall MSDN Library from 10/2001 - so that's what I was trying to find. I'll contact MS to see if they can get me anything or check around here to see if anyone has a CD. Thanks for your help and sorry this has been so confusing - this is my first time posting on this site. Thanks again!.
Sent via Developersdex. Ken Halter 11/7/2007, 8:15 น. 'C Rule' wrote in message news:[email protected].
I'll contact MS to see if they can get me anything or check around here to see if anyone has a CD. If you downloaded VB as part of your subscription, no need to contact anyone. MSDN 10/2001 is available too.
When you log on to MSDN, go to the downloads section, You should see 'MSDN Library' in the list. Click on that and the first item in the list is '2001-10 MSDN Library October 2001' - Ken Halter - MS-MVP-VB - Please keep all discussions in the groups.
In Loving Memory - Karl E. Peterson 11/7/2007, 9:47 น. MikeD wrote: Also, you should verify it's actually the disc and not your drive that's the problem. Try using the disc in another drive (friend's computer, work computer, etc.). Unless you're abusing a CD or DVD, they don't normally just 'get' corrupted. Y'know, awhile ago I found that quite a number of CDs I had burned on Windows 2000 were not readable - at all - on any Windows XP machine I tried them on. Stick 'em back in a W2K machine, real.or.
virtual(!), and they were totally readable. Yeah, pixxed me off, alright.NET: It's About Trust!
Peterson 11/7/2007, 9:48 น. Ken Halter wrote: 'C Rule' wrote in message news:[email protected]. I'll contact MS to see if they can get me anything or check around here to see if anyone has a CD. If you downloaded VB as part of your subscription, no need to contact anyone.
MSDN 10/2001 is available too. Oh good lord, wasn't that.also. one of the very first responses s/he got??? What.is. it with these, that they can't be bothered to.read.? -.NET: It's About Trust!
MikeD 11/7/2007, 11:03 น. MikeD wrote: 'Karl E.
Peterson' wrote. MikeD wrote: Also, you should verify it's actually the disc and not your drive that's the problem. Try using the disc in another drive (friend's computer, work computer, etc.). Unless you're abusing a CD or DVD, they don't normally just 'get' corrupted. Y'know, awhile ago I found that quite a number of CDs I had burned on Windows 2000 were not readable - at all - on any Windows XP machine I tried them on. Stick 'em back in a W2K machine, real.or. virtual(!), and they were totally readable.
Yeah, pixxed me off, alright. I wasn't real clear on this, but I wasn't talking about CDs or DVDs that you burned yourself. I was talking about commercially purchased CDs and DVDs. Yeah, I wasn't too clear either.
I understood what you were saying, but it brought this instance to mind. Yeah, I'm still really pixxed about it. I mean, how.dare. they? Heck, I had an external USB CDROM drive - plug it into XP, and it couldn't read the disks; plug it into W2K, and it could!
-.NET: It's About Trust! Stefan Berglund 11/7/2007, 12:21 น. On Wed, 11 Jul 2007 11:51:08 -0700, 'Karl E. Peterson' wrote: in Yeah, I wasn't too clear either.
I understood what you were saying, but it brought this instance to mind. Yeah, I'm still really pixxed about it. I mean, how.dare. they?
Heck, I had an external USB CDROM drive - plug it into XP, and it couldn't read the disks; plug it into W2K, and it could! That sorta falls into the category of live and learn but maybe you'll consider using a third party burner instead of the mickey mouse software microsoft provides for that purpose. I can't count how many CDs/DVDs I trashed futilely trying to burn using microsoft's copy it into the burn buffer folder crap. I now use CDBurnerXP Pro 3 and I've had zero problems since April 24, 2006. I have clients with W2K, XP, and Vista and I burn on XP Pro and nary a problem.
The only problem was that they were planning a.NET version - never mind I see that version 3.0.116 is still available for free download. I use it to create an ISO image and then I use it to burn the ISO. And it's quick as well. Stefan Berglund Karl E. Peterson 11/7/2007, 12:33 น. Stefan Berglund wrote: 'Karl E.
Peterson' wrote: Yeah, I wasn't too clear either. I understood what you were saying, but it brought this instance to mind. Yeah, I'm still really pixxed about it. I meanhow.dare. they? Heck, I had an external USB CDROM drive - plug it into XP, and it couldn't read the disks; plug it into W2K, and it could! That sorta falls into the category of live and learn but maybe you'll consider using a third party burner instead of the mickey mouse software microsoft provides for that purpose.
These were burned with Nero and/or Roxio. Couldn't be read in XP. What's the lesson there?
-.NET: It's About Trust! Stefan Berglund 11/7/2007, 13:11 น. Stefan Berglund wrote: 'Karl E. Peterson' wrote: Stefan Berglund wrote: 'Karl E. Peterson' wrote: Yeah, I wasn't too clear either. I understood what you were saying, but it brought this instance to mind.
Yeah, I'm still really pixxed about it. I mean, how.dare. they? Heck, I had an external USB CDROM drive - plug it into XP, and it couldn't read the disks; plug it into W2K, and it could! That sorta falls into the category of live and learn but maybe you'll consider using a third party burner instead of the mickey mouse software microsoft provides for that purpose. These were burned with Nero and/or Roxio.
Couldn't be read in XP. What's the lesson there?
OK, sorry. I ASSuMEd you were using microsoft software. NP, and no-friggin-sheet. But I'd look at the devices real close too. Can you burn in XP and read in W2K? Using the same software? It's entirely possible that microsoft has a hand in it but there's an awful lot of other variables in the mix too.
I tried.really. hard to eliminate anything that could've possibly confused the issue. What it comes down to is, XP just doesn't 'like' some discs burned with W2K.
I mean, I even have other discs (from the same retail spindle!) that work on both, if burned in XP. I moved a single piece of hardware back and forth. Used the same software on both. That playing field was as level as I could imagine making it.NET: It's About Trust! Stefan Berglund 11/7/2007, 17:03 น.
On Wed, 11 Jul 2007 13:47:02 -0700, 'Karl E. Peterson' wrote: in I tried.really. hard to eliminate anything that could've possibly confused the issue. What it comes down to is, XP just doesn't 'like' some discs burned with W2K.
I mean, I even have other discs (from the same retail spindle!) that work on both, if burned in XP. I moved a single piece of hardware back and forth. Used the same software on both.
That playing field was as level as I could imagine making it. Then you answered my next question. I remember way back in 1999 or so burning CDs that couldn't be read on a really old machine that had been converted to Windows 98 but that was because I burned at a speed faster than the ancient could read. Yep, that pretty much says they did something to XP. Odd, really odd. Did you by chance try the same experiment with a second piece of hardware on both OSes?
- Stefan Berglund Pop` 11/7/2007, 17:28 น. I can toss one other possiblility in for you, though it's probably not relevant. During the flurry about that time in the late 90's, when everyone was scrambling to print their own 'pretty' CD labels, it was discovered that some of the adhesives could damage the CD's usability. I was part of the crowd and did use lables on some of the CDs I made for other people - nice and professional looking, you know, stuff like that. I became a little more of a believer when finally someone did some scientific analysis (forget where; it's buried in my archives now) that seemed to settle the matter. I do know that the only CDs I've ever had 'go bad' had those printed lables I placed on them.
For a lot of reasons, not to mention spindle speeds, that kind of labelling went the way of the dinosaur, but. Thought I'd mention it just in case it was common to something for you. I also seem to recall that Roxio, around version 5.5 or so, had some sort of a problem, too that was fixed in following revs.
Never heard of Nero et al having the same problem. Roxio's problem had something to do with whether or not you closed the CD just so it could be played on 'most' CD players or you completelyh closed it to prevent future writing also; they're two different choices, though I've never seen a difference in the CD's they produce. Just my 2 ¢ worth Pop` Karl E. Peterson 11/7/2007, 17:38 น. Stefan Berglund wrote: 'Karl E. Peterson' wrote: I tried.really. hard to eliminate anything that could've possibly confused the issue.
![Visual basic 6.0 msdn library Visual basic 6.0 msdn library](/uploads/1/2/5/3/125381334/315765327.jpg)
What it comes down to is, XP just doesn't 'like' some discs burned with W2K. I mean, I even have other discs (from the same retail spindle!) that work on both, if burned in XP. I moved a single piece of hardware back and forth. Used the same software on both. That playing field was as level as I could imagine making it.
![Msdn visual basic 6 download Msdn visual basic 6 download](http://www.kimgentes.com/storage/msdn-vb6-8.png?__SQUARESPACE_CACHEVERSION=1411054907622)
Then you answered my next question. I remember way back in 1999 or so burning CDs that couldn't be read on a really old machine that had been converted to Windows 98 but that was because I burned at a speed faster than the ancient could read. Yep, that pretty much says they did something to XP. Odd, really odd. Did you by chance try the same experiment with a second piece of hardware on both OSes? Not with an identical piece of hardware.
I was convinced though. I tried the discs in probably close to two dozen machines, looking for patterns. Both with internal drives, and with an external USB drive that I could move between them. Dunno what was odd about these discs, but they simply couldn't be read by.any. XP box, although.any. 2k box read them just fine. I couldn't repro the situation, either, with newly burnt discs, so I'm left frustrated.
The question is, how much old data is 'safely' backed up to CD, only to be wanted again after all 2k machines have been retired/updated? Really sucks.NET: It's About Trust!
Peterson 11/7/2007, 17:41 น. Pop` wrote: I can toss one other possiblility in for you, though it's probably not relevant. During the flurry about that time in the late 90's, when everyone was scrambling to print their own 'pretty' CD labels, it was discovered that some of the adhesives could damage the CD's usability.
I was part of the crowd and did use lables on some of the CDs I made for other people - nice and professional looking, you know, stuff like that. I became a little more of a believer when finally someone did some scientific analysis (forget where; it's buried in my archives now) that seemed to settle the matter. I do know that the only CDs I've ever had 'go bad' had those printed lables I placed on them. For a lot of reasons, not to mention spindle speeds, that kind of labelling went the way of the dinosaur, but. Thought I'd mention it just in case it was common to something for you.
No labels on these, though I fell for them too for awhile. There was Sharpie ink, of course, identifying the content. Hard to see how either a label or ink could affect discs on XP only, though, eh?
I also seem to recall that Roxio, around version 5.5 or so, had some sort of a problem, too that was fixed in following revs. Never heard of Nero et al having the same problem. Roxio's problem had something to do with whether or not you closed the CD just so it could be played on 'most' CD players or you completelyh closed it to prevent future writing also; they're two different choices, though I've never seen a difference in the CD's they produce. There's a good chance these were burnt with Roxio (the freebie Dell version du jour).
I honestly can't remember.NET: It's About Trust! Jim Carlock 12/7/2007, 1:52 น. Peterson' wrote.: The question is, how much old data is 'safely' backed up to CD, only: to be wanted again after all 2k machines have been retired/updated?: Really sucks. I've had great success with burnatonce. It's kind of cryptic, alot of different parameters to get configured, but it works. I've created plenty of disks on XP that were readable on Win2K. I'm not sure if I've done it the other way around though.
I only use a CD burner and then pop CDs into CD/DVD readers. The CDs are readable on NT4, 9x and Win2K. I've used that software for a very long time (since 2000 or 2001) with no need for any other software. Don't know if it (or how it) works with DVD burners. Jim Carlock Post replies to the group. Peterson 12/7/2007, 9:44 น.
On Thu, 12 Jul 2007 09:44:31 -0700, 'Karl E. Peterson' wrote: in Thanks for the recommend, Jim. I'll keep that tucked away.
I don't think I'm still having these issues. As I said, I can't seem to repro the situation with fresh burns. But what kills me is the data that's already 'backed-up' on discs that are not readable on XP systems. Won't know what they are, until they're needed, either.
I'm still chewing on this unhappy prospect and the only thing that makes sense is that perhaps it's related to microsoft's descent into the ill fated DRM abyss. Stefan Berglund Karl E. Peterson 12/7/2007, 11:23 น. Stefan Berglund wrote: 'Karl E. Peterson' wrote: Thanks for the recommend, Jim. I'll keep that tucked away. I don't think I'm still having these issues.
As I said, I can't seem to repro the situation with fresh burns. But what kills me is the data that's already 'backed-up' on discs that are not readable on XP systems.
Won't know what they are, until they're needed, either. I'm still chewing on this unhappy prospect and the only thing that makes sense is that perhaps it's related to microsoft's descent into the ill fated DRM abyss. It's funny/ironic you'd say that, actually.
The failing discs all contained MP3s. (Although other, contemporaneously burned discs, did as well.
Again, not an identifiable failure-inducing trait.) -.NET: It's About Trust! Jim Carlock 12/7/2007, 19:04 น.
Peterson' wrote: Thanks for the recommend, Jim. I'll keep that tucked away. I don't think I'm still having these issues. As I said, I can't seem to repro the situation with fresh burns. But what kills me is the data that's already 'backed-up' on discs that are not readable on XP systems. Won't know what they are, until they're needed, either.
Ok, I'll try to keep this short and to the point. Back in 1999 'I' literally built close to 1000 Windows 98 systems and/or WinNT4 systems. The company that I worked for loved me because their return rate went down from 50% to less than 1%. They stated their prior return rates were very high and 50% might be a small exaggeration (then it again it might have actually been higher). Sometimes I want to exaggerate something to get a point across, but I don't have to do that here. (And if anyone would like to know what made me better than the guy I replaced, it's an easy question to answer. Feel free to ask.
It's not a fault upon the individual, he just didn't know what I knew.:-)) I ran into a batch of CD Writers/DVD Readers made by Creative Labs that could read most DVDs. However, one specific model made by Creative Labs (yeah, the Sound Blaster folks who I respected highly at the time because of all their ISA sound cards), Creative Labs was venturing into the CD-ROM market and I believe they ended up buying CD/DVD players made by other companies and then they put their name on the items (that occured with quite a bit of other electronic computer hardware, especially those PCI sound cards). I ended up calling Creative Labs multiple times, talking to multiple 'technicians' (salespeople) at Creative Labs. I knew that DVDs were growing in size (meaning more and more data was getting put on them). The 'technicians' were really just salespeople trying to sell things and they did not know what I knew. They were used to talking to other technicians that did not read up on the latest events in DVDs (I ended up with a subscription to some engineering journal that was oriented to engineers in the laser field and the articles at that time talked about CD and DVD formats). It was the hardware that was faulty and the sales people held no clue at what was going on in the DVD market.
DVDs standards started off at holding like 1GB of data on disks, then it went up to 2GB, then another method provided 4GB and I think it peaked out at 8GB. The numbers are probably not exactly correct, so take it just as a description to give an idea of how the DVD technology developed. The DVD format was not the only problem. CD-ROMs were made to support 600MB, then 700MB, then 750MB, then.
And again, the numbers are probably a little off, but that's the way it went, smaller and smaller tracks, better electronics, sensors. Then there were some CD writers (sometimes a whole model line) that could only read the CDs they created, other CD players were unable to read the CDs created by those bad 'models' or 'drives'. Those CDW drives were a major pain to deal with and there were alot of them out there manufactured under a whole bunch of different names (most were unknown 'no name' cheap drives but some others carried labels by well-known companies, i.e. Creative Labs). By the way, I own a Creative DVD player that works great! And this isn't to bash Creative Labs.
So what I recommend, when buying a new CD/DVD writer, is to do a serious of read tests (some of the real-long movie DVDs that hold a long movie are good to see if the player will read the higher formats). Make sure the DVD player can read your old CDs and DVDs.
Then do a series of write tests, where you write to a DVD or CD and then test that media in an old Windows 9x system to see if it can read it, and then test it in another system. Two or three different machines. If all read well, you've probably got a great drive and have no worries. At least that's based upon my own personal experience.
If one of the other drives can't read the disk, take the new drive back as soon as possible and ask for a replacement. It's a pain in the rump way to do things but that's the only way to do it, as far as I'm concerned. Testing to make sure that older systems can read and copy from a FULL data disk is a requirement. Test the audio burn and playback as well. And for DVDs, the video recording and playback is a must as well.
Trust no one? Trust no one. Test everything. And one last thing I'll mention, is that burners may write very well at the lower speed settings and then go to hell when you try to get them to write at their 'fastest' setting. So be prepared to do ALOT of returns if you're testing things on their 'fastest' write settings. I've seen a few drives that don't work at their fastest settings but work very well at slower settings. So whatever X they put on the drive may be a lie and if you're buying cheap drives be prepared to use something lower than their advertised fastest speed.
It's a good idea to test all purchased readers. CD writers (and/or DVD writers) end up as a special class of goods that require ALOT of special attention after they're bought.
All disk drives fall into this special class of goods, but my own personal experience really indicates that special tests need to get performed to determine if a new drive really works. Jim Carlock HeadShred 20/7/2007, 14:36 น. Similar problem, my 2 MSDN Library cds have disappeared and VB Studio 6 has been installed on my new office pc without them. Is there anything I can do with the files from my old pc? I've tried copying them across the network into an identical directory structure, but when I try to execute HELP from within VB 6, it says the files are missing.
Something to do with the setup script I guess. Any tricks anyone? Thanks 'MikeD' wrote: 'Raj' wrote in message [email protected]. Hi AllFrom where can i download msdn help setup for vb 6.0. Can any one tip me on this please it would be of great help. Nowhere that I know of.at least legally.unless you're an MSDN Subscriber.
- Mike Microsoft MVP Visual Basic MikeD 20/7/2007, 15:09 น. 'HeadShred' wrote in message news:[email protected]. Similar problem, my 2 MSDN Library cds have disappeared and VB Studio 6 has been installed on my new office pc without them. Is there anything I can do with the files from my old pc? I've tried copying them across the network into an identical directory structure, but when I try to execute HELP from within VB 6, it says the files are missing. Something to do with the setup script I guess.
Any tricks anyone? None that I know of. The thing is, there are support DLLs that need registered and other entries in the Registry that must exist.
I think there's even config/INI files that must have the proper settings (again, created during installation). Unless you properly install MSDN Library, you're not going to have these. The best advice I can give you is to look long and hard for your original MSDN Library discs. Not intending to be mean or come down on you in any way, but how can you lose something so important? What's more baffling is why didn't you have your MSDN Library discs stored right with your VB6/VS6 disc(s)? - Mike Microsoft MVP Visual Basic HeadShred 20/7/2007, 15:20 น.
'HeadShred' wrote in message news:[email protected]. Similar problem, my 2 MSDN Library cds have disappeared and VB Studio 6 has been installed on my new office pc without them. Is there anything I can do with the files from my old pc? I've tried copying them across the network into an identical directory structure, but when I try to execute HELP from within VB 6, it says the files are missing. Something to do with the setup script I guess.
Any tricks anyone? Thanks It wouldn't be easy, but it wouldn't be impossible. Through diligence examining the folders, dependancies, and registry, it should be possible to do it manually.
Good Luck Stefan Berglund 20/7/2007, 17:01 น. On Fri, 20 Jul 2007 14:36:03 -0700, HeadShred wrote: in Similar problem, my 2 MSDN Library cds have disappeared and VB Studio 6 has been installed on my new office pc without them. Is there anything I can do with the files from my old pc? I've tried copying them across the network into an identical directory structure, but when I try to execute HELP from within VB 6, it says the files are missing.
Something to do with the setup script I guess. Any tricks anyone? You could try installing HTML Help Workshop and see what happens. I'd think that at least you'd then have the tools for displaying help. I just used HTML Help Workshop to display the.chm files from the MSDN folder on the MSDN DVD.
Then copy all the.chi and.chm files from the other machine using the same folder structure. On my machine the.chi and.chm are not on my hard disk but rather on the DVD. You might have to figure out some missing registry settings if it doesn't work straight off but that should be made much easier by having a working machine to examine. Stefan Berglund HeadShred 20/7/2007, 19:04 น. 'dpb' wrote in message news:[email protected].
Don't think it is available as download VB6 Help Files.MS is still trying to find the magic silver bullet or wooden stake to kill the beast VB6 entirely but hasn't been able to totally succed.:). But they seem to be much more frightened of killing VBA, which is still provided with MS Office 2007 applications, apart from their little experiment in which they've killed the macro recorder in PowerPoint 2007 just to test the water;-) Mess about too much with the toys that the boss plays with and he might just decide to buy his company's software elsewhere;-) Mike ASANT KUMAR SWAIN 3/11/2007, 8:56 น. Toilet Paper Burner? Toy Poodle Buyer?
Tough Poo, Bonehead? Total Porridge Burnout?
Tricky Panda Bugler? Ticklish Pig Boycott?
Truculent Pomeranian Biscuits? Tinned Pickled Beets? Tom Passes Beans? Tender Pudgy Barmaids?
Terribly Pugnacious Badger Torrential Puddling Barf? Typical Programming Blunder? The initials 'TPB' mean ever so many things to me.:) - Tim Rude (remove NOSPAM. For correct email address) 'Karl E. Peterson' wrote in message news:%23NbFt6%[email protected].
Barani kumar 5/2/2008, 2:29 น. I don't know whether this will help you, but you can download later versions of the Win32 SDK. I don't think that VB6 specifically is still in there, but most everything else should be. I downloaded the Server 2003 SDK awhile back out of curiosity.
It was offered on. (!) The only catch is that MS created a new, incompatible HTML help format to go with.Net.
I found a free program called HelpExplorer that reads the files, but I gather that if you want a convenient GUI with a master index then you have to install some sort of.Net IDE. Bill McCarthy, 8:05 น. 'mayayana' wrote in message news:[email protected]. I don't know whether this will help you, but you can download later versions of the Win32 SDK. I don't think that VB6 specifically is still in therebut most everything else should be.
Why are you pointing him to windows API documentation? How could you possibly think that the win32 SDK helps him with VB6 documentation? I downloaded the Server 2003 SDK awhile back out of curiosity. It was offered on. (!) Oh my, that's hysterical.
Rather than get the SDK's from Microsoft, you wait till you see something somewhere else. Any way, enough of this nonsense, time for some FACTS: The VB6 documentation is not available for download (at least not legally).
The VB6 documentation however can still be found on line at: expvb, 8:06 น. Rather than get the SDK's from Microsoft, you wait till you see something somewhere else. Here's a link: I don't remember exactly what the reason was that I didn't get it from MS.
Looking now I find one page that offers either a web install or a DVD ISO. Another link requires installing the WGA spyware. While CNet was offering a CD ISO. Maybe MS had that, too.
I don't know. But I'm not surprised that it was easier to find on a 3rd-party site than it was on. Bill McCarthy, 9:27 น.
'mayayana' wrote in message news:[email protected]. Rather than get the SDK's from Microsoft, you wait till you see something somewhere else. Here's a link: I don't remember exactly what the reason was that I didn't get it from MS.
You're kidding us all right? Surely you aren't suggesting the original psoter download over 400 MB when that does NOT contain the VB6 help documentation.
How off topic can you possibly get? Mayayana, 9:48 น. Surely you aren't suggesting the original psoter download over 400 MB when that does NOT contain the VB6 help documentation. The OP asked for MSDN for VB6. I find that I rarely look up VB-specific items in MSDN. I typically am looking up API calls, IE DOM details, etc. I actually only downloaded the newer version out of curiosity, as I like to avoid code that won't run on Win9x, so I don't need updated docs.
But to the extent that I looked over the 2003 SDK it seemed to include most older docs. So, to answer your question, if I were the OP, and I had no copy of MSDN at all, then I'd be very interested in the SDK download. It at least beats trying to find information on the MS website, which often requires slogging through 3 or 4 unnecessary pages for each bit of info.
Assuming that one can find things at all. Actually, I can't remember the last time I even tried to find something by starting at MSDN online. It's much easier to just use Google rather than the MS site. Their site is disorganized, there are loads of dead links, and their search is very poor.
(And for anyone without high-speed the MS pages are completely unusable. It just takes too long to download bloated, 65 KB, superfluous pages that often end up containing only 3 lines of actual text.) I know you don't care about any of this, Mr. Bill, but sometimes your nonsensical posts provide convenient segues to provide more info. To someone who might benefit from it.:) Bill McCarthy, 10:02 น. 'mayayana' wrote in message news:[email protected]. The OP asked for MSDN for VB6.
I find that I rarely look up VB-specific items in MSDN. The poster asks for MSDN.for VB6. You then come back with some statement that you don't use MSDN for VB6. I typically am looking up API calls, IE DOM details, etc. Which isn't VB6. Hey why don't we include.NET in there too, I'd bet you'd like that;) It at least beats trying to find information on the MS website Actually no it doesn't because the VB6 documentation is only available online if you don't have the original CD's.
MSDN subscribers can of course still download it, but if he isn't a MSDN subscriber he has to use online. As to the rest of your rant, I'm sure you thought it was cute, but it was just completely off topic to the original question. Even if we were to assume you honestly somehow thought the original poster was after API documentation for Windows, you should have pointed him to current versions or asked for which version of windows etc, instead of picking some download that wasn't even on Microsoft's site. As others have posted here, finding the SDKs for download from Microsoft's downloads is incredibly easy once you decide which of the many SDKs you want.
But back to the topic, none of them(other than msdn subscriber downloads) contain the VB6 documentation. Mike Williams, 10:25 น. On Mon, 23 Mar 2009 15:29:17 -0700, 'Karl E. Peterson' wrote: What's up with these Developersdex dufuses (dufii?) anyway? I've reported DevDex posts to them many times and they still won't a) answer me, and/or b) stop/block 'illegal' posts asking for 'wares' copies of MSDN, VS, etc.