p2p.wrox.com Forums

p2p.wrox.com Forums (http://p2p.wrox.com/index.php)
-   All Other Wrox Books (http://p2p.wrox.com/forumdisplay.php?f=116)
-   -   Visual Basic .NET Solutions Toolkit: 30 Practical (http://p2p.wrox.com/showthread.php?t=4087)

qursaan September 20th, 2003 06:01 AM

Visual Basic .NET Solutions Toolkit: 30 Practical
this Book is hiden from the site?:([?][?][?]
or can any one past the its links[:0]

Q u r S a a n

Imar September 20th, 2003 01:56 PM

Hi there,

Please check out this post for an answer:




Imar Spaanjaars
Everyone is unique, except for me.

pberce April 12th, 2004 08:06 AM


Scorp February 7th, 2010 09:55 PM

Complete lack of support
Who could be surprised, I suppose. Company A sells the code to company B who publishes it, having not a clue appparently as to how error-ridden the book is. Then when it does come to any light at all, get rid of all references to it, because hey it's not "our" code, right? Of course Company A did know what a P.O.S. it was that they sold to Company B, so of course they warrant no support for it either.

Hey, what's money between customer and seller, though right? Sure.

I'll never buy another Wrox publication again. Period.

jminatel February 8th, 2010 10:09 AM

For the record: we'd support the code if we were allowed to. However, "company B" legally prohibits us from providing the code they bought. They bought it, it's theirs. It's one thing for them to say "sorry, we can't answer any questions about this code." It's another to not distribute it from their website and to prohibit us from distributing it as well. And they know that by not supporting it, they make us look bad because it's our name on it not theirs.

Is this about the Visual Basic .NET Solutions book from 2002 in the thread title? If so, you might try contacting the author through his contact information on his blog:

If it's a different book, have you tried tracking down the author?

Scorp February 9th, 2010 10:42 PM

I have a good number of publications from Wrox that I've acquired over the years. I've ran into this very situation several times before, including a recent search I did on a different title. While searching, I came across this thread and decided to check the 2002 print of the solutions toolkit. My frustration wasn't/isn't tied to this specific title, but in an overal picture. It just happened to be this title thread in which I decided to post, because frankly I'm quite tired of the modern-day pass-the-buck society we've come to.

I understand about property and intellectual rights to property, hence I understand why your hands are tied on this. What I dont understand is why, when these packages are bought and sold, there seems to be no accountability for supporting the customers who have spent the money on it. I'm hard-pressed to believe that the small amount of space on a support site to house supporting code would be a deal-breaker for any contractual purchase. Perhaps I'm too old-school for believing a company should consider it's customers.

I also understand that this title is probably considered to be an aged publication, and time-limited support is commonplace. The flip-side to that, however, is that there is still a vast group of developers publishing apps with Visual Basic 6. Not because they can't learn .NET, but because it saves the hassles of .NET installation confirmation and even more so to avoid the whole JIT compiling scenario. This particular title might be 8 years old, it's not "aged" in the sense that some might believe, which brings my underlying belief that someone should be able to require at least a minimal level of support for it as a part of any purchase contract.

I don't need to contact the author, as over the years I've already rewritten code that far surpasses anything this title had. I also would never expect to have to hunt down an author for a title which strongly advertises it's own support, ie:

Right on the front cover:
"Wrox technical support at: support@wrox.com"
"Updates and source code at: www.wrox.com"
"Peer discussion at: p2p.wrox.com"

The Support and Errata section of the appendix is completely laden with direction to Wrox.com

I don't think something should be advertised that isn't intended to be provided more than a short term. But hey this is all merely my opinion. Some will agree, some won't. C'est la vie.

jminatel February 10th, 2010 07:07 PM

Scorp: This was a pretty unusual situation. Essentially what happened was "old" Wrox's owners went bankrupt (receivership) in 2003. The old employees showed up one day and their jobs were gone.
A receiver/liquidator took over to sell off their assets. We bought the name, the best-selling books at the time, the web sites, etc.
What we didn't anticipate was that after that, the receiver/liquidator would sell the rights and inventory to the remaining older books and books that didn't sell as well to another publisher.
We initially attempted to distribute the code to all the old books, thinking it was in everyone's best interest, and were quickly told to stop by the other publisher. Unfortunately for us and for "Wrox" customers, whether you'd already bought the book or found it a week or 7 years later in a bargain bin, it still said "come to Wrox and get the code."
I don't know why the other publisher stopped distributing the code for the books they bought. I know they had a server crash at one point and when their code pages came back, that particular code was no longer there.
So yes, you nailed it when you said our hands are tied. And you're absolutely right that there's a huge VB6 community (as just one example) where the 10 year old books are just as useful today as they were 10 years ago. And we can't do anything to help.
What I do think we've done is the best job possible supporting the Wrox books we bought and the new Wrox books we've published in the last 7 years. I hope that's enough but I know that for some people it won't be.

All times are GMT -4. The time now is 04:10 AM.

Powered by vBulletin®
Copyright ©2000 - 2019, Jelsoft Enterprises Ltd.
© 2013 John Wiley & Sons, Inc.