Home > Archive > Visual Basic > December 2005 > How do I output "quotes"
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
How do I output "quotes"
|
|
|
| Apologies if this is a stupid question but I am not a programmer :o), and am
guessing this is probably very basic, but how do I output a quote mark (")
when writing to a file?
I am trying to read in a fixed length data file and reformat it ouputting
the relevant data in a delimitted format where the fields need to be
surrounded by quotes and seperated by commas. I can get it to do everything
except output the quotes. I am guesing I could perhaps put the string
together using the ASCII code #34 but I'm not sure how to do this. Can anyone
point me in the right direction or suggest an alternative strategy?
Thanks
Dave
| |
| Howard Kaikow 2005-12-13, 7:55 am |
| For example:
Dm strTitle as String
strTitle = CHR$(34) & "Pizza is yummy!" & CHR$(34)
--
http://www.standards.com/; See Howard Kaikow's web site.
"Dave" <Dave@discussions.microsoft.com> wrote in message
news:F5D962A9-2982-47A1-BC97-DECCD0C5B96D@microsoft.com...
> Apologies if this is a stupid question but I am not a programmer :o), and
am
> guessing this is probably very basic, but how do I output a quote mark (")
> when writing to a file?
>
> I am trying to read in a fixed length data file and reformat it ouputting
> the relevant data in a delimitted format where the fields need to be
> surrounded by quotes and seperated by commas. I can get it to do
everything
> except output the quotes. I am guesing I could perhaps put the string
> together using the ASCII code #34 but I'm not sure how to do this. Can
anyone
> point me in the right direction or suggest an alternative strategy?
>
> Thanks
>
> Dave
| |
| Mark Alexander Bertenshaw 2005-12-13, 7:55 am |
| Try these:
Debug.Print """"
Debug.Print """Double quoted string"""
Debug.Print "Double ""quoted"" string"
Alternatively, you can use a Chr$(34) to retrieve this character.
Even more alternatively, use the Write statement, rather than Print, because
it automatically inserts commas and quotes.
--
Mark
"Dave" <Dave@discussions.microsoft.com> wrote in message
news:F5D962A9-2982-47A1-BC97-DECCD0C5B96D@microsoft.com...
> Apologies if this is a stupid question but I am not a programmer :o), and
am
> guessing this is probably very basic, but how do I output a quote mark (")
> when writing to a file?
>
> I am trying to read in a fixed length data file and reformat it ouputting
> the relevant data in a delimitted format where the fields need to be
> surrounded by quotes and seperated by commas. I can get it to do
everything
> except output the quotes. I am guesing I could perhaps put the string
> together using the ASCII code #34 but I'm not sure how to do this. Can
anyone
> point me in the right direction or suggest an alternative strategy?
>
> Thanks
>
> Dave
| |
|
| Hi
there are at least 3 ways to do this
1) Chr$(34)
2) """" (yes 4 quotes not 3)
3) use a constant like:
Private Const Quot = """"
I like the constant because it is easiest to read, but if it is only needed
in a few places then the either of the other methods are fine.
Best Regards
Dave O.
"Dave" <Dave@discussions.microsoft.com> wrote in message
news:F5D962A9-2982-47A1-BC97-DECCD0C5B96D@microsoft.com...
> Apologies if this is a stupid question but I am not a programmer :o), and
> am
> guessing this is probably very basic, but how do I output a quote mark (")
> when writing to a file?
>
> I am trying to read in a fixed length data file and reformat it ouputting
> the relevant data in a delimitted format where the fields need to be
> surrounded by quotes and seperated by commas. I can get it to do
> everything
> except output the quotes. I am guesing I could perhaps put the string
> together using the ASCII code #34 but I'm not sure how to do this. Can
> anyone
> point me in the right direction or suggest an alternative strategy?
>
> Thanks
>
> Dave
| |
| J French 2005-12-13, 7:55 am |
| On Tue, 13 Dec 2005 01:56:03 -0800, "=?Utf-8?B?RGF2ZQ==?="
<Dave@discussions.microsoft.com> wrote:
>Apologies if this is a stupid question but I am not a programmer :o), and am
>guessing this is probably very basic, but how do I output a quote mark (")
>when writing to a file?
>
>I am trying to read in a fixed length data file and reformat it ouputting
>the relevant data in a delimitted format where the fields need to be
>surrounded by quotes and seperated by commas. I can get it to do everything
>except output the quotes. I am guesing I could perhaps put the string
>together using the ASCII code #34 but I'm not sure how to do this. Can anyone
>point me in the right direction or suggest an alternative strategy?
Private Sub Command1_Click()
Dim S$, T$
T$ = "Test"
' Method 1
S$ = """" + T$ + """"
Me.Print S$
' Method 2
S$ = Chr$(34) + T$ + Chr$(34)
Me.Print S$
' Method 3
Const vbQuote = """"
S$ = vbQuote + T$ + vbQuote$
Me.Print S$
' Method 4 (the one I prefer)
Me.Print Quotes(T$)
End Sub
Public Function Quotes$(T$)
Quotes$ = Chr$(34) + T$ + Chr$(34)
End Function
| |
|
| Thanks guys - I knew it was a dumb question! Just had that "Of course it is"
feeling - Doh! How daft do I feel? Have been struggling with that for ages.
Thanks
:o)
"Mark Alexander Bertenshaw" wrote:
> Try these:
>
> Debug.Print """"
> Debug.Print """Double quoted string"""
> Debug.Print "Double ""quoted"" string"
>
> Alternatively, you can use a Chr$(34) to retrieve this character.
>
> Even more alternatively, use the Write statement, rather than Print, because
> it automatically inserts commas and quotes.
>
> --
> Mark
>
> "Dave" <Dave@discussions.microsoft.com> wrote in message
> news:F5D962A9-2982-47A1-BC97-DECCD0C5B96D@microsoft.com...
> am
> everything
> anyone
>
>
>
| |
|
| > Private Sub Command1_Click()
> Dim S$, T$
>
> T$ = "Test"
>
> ' Method 1
> S$ = """" + T$ + """"
> Me.Print S$
>
> ' Method 2
> S$ = Chr$(34) + T$ + Chr$(34)
> Me.Print S$
>
> ' Method 3
> Const vbQuote = """"
> S$ = vbQuote + T$ + vbQuote$
> Me.Print S$
>
> ' Method 4 (the one I prefer)
> Me.Print Quotes(T$)
>
>
> End Sub
>
> Public Function Quotes$(T$)
> Quotes$ = Chr$(34) + T$ + Chr$(34)
> End Function
Never use + for joining strings, always use &
Dave O.
| |
| J French 2005-12-13, 7:55 am |
| On Tue, 13 Dec 2005 11:06:06 -0000, "Dave" <nobody@nowhere.com> wrote:
<snip>
>Never use + for joining strings, always use &
I disagree
The '&' String concatonator is a relatively new addition to BASIC
Since '+' has been around for many years before VB, I'm perfectly
happy using what I've used for 28 years
I also intensely dislike the sloppy type conversion :-
Private Sub Command1_Click()
Dim S$, T&
S$ = "Test"
S$ = S$ & T&
Me.Print S$
End Sub
To be honest I can't see any reason why MS introduced '&'
- it is a nasty construct, alien to BASIC and can disguize typing
errors
And before you pounce on the use of '$' and '&' as suffixes, think
about :
Left$(), Mid$(), Right$()
also
Const X = &hFFFF&
MS is consistently inconsistent
| |
|
|
"J French" <erewhon@nowhere.uk> wrote in message
news:439eb124.351137497@news.btopenworld.com...
> On Tue, 13 Dec 2005 11:06:06 -0000, "Dave" <nobody@nowhere.com> wrote:
>
> <snip>
>
>
> I disagree
>
What does "4" + 5 give you?
9 or 45
With + you have no way to tell, with & you know what it'll do. Obviously one
shouldn't mix types like in that example but to avoid ambiguity one should
use the correct syntax. VB allows the use of + just for compatability with
old code.
Dave O.
| |
| Rick Rothstein [MVP - Visual Basic] 2005-12-13, 6:56 pm |
| > 3) use a constant like:
> Private Const Quot = """"
Just out of curiosity, why wouldn't you go for the extra letter and make
that
Private Const Quote = """"
instead?
Rick
| |
|
| Rick
2 reasons
1 - Laziness
2 - Avoid the potential of a conflict with a reserved word - OK "Quote"
probably isn't a reserved word, but that's the point, if I avoid English
words then I don't have to check to see if they are reserved.
Best Regards
Dave.
"Rick Rothstein [MVP - Visual Basic]" <rickNOSPAMnews@NOSPAMcomcast.net>
wrote in message news:%237swRU$$FHA.3136@TK2MSFTNGP15.phx.gbl...
>
> Just out of curiosity, why wouldn't you go for the extra letter and make
> that
>
> Private Const Quote = """"
>
> instead?
>
> Rick
>
>
| |
| Karl E. Peterson 2005-12-13, 6:56 pm |
| J French wrote:
> To be honest I can't see any reason why MS introduced '&'
> - it is a nasty construct, alien to BASIC and can disguize typing
> errors
Why, *how else* might they have rolled out ETC in VB4, without it???
--
Working without a .NET?
http://classicvb.org/
| |
| Randy Birch 2005-12-13, 9:55 pm |
| Personally, in the couple of apps I've had to do this in when working with
converting HTML I use just a Const q = .... Saves typing and being short
keeps more of the long and complicated HTML lines in view.
--
Randy Birch
MS MVP Visual Basic
http://vbnet.mvps.org/
----------------------------------------------------------------------------
Read. Decide. Sign the petition to Microsoft.
http://classicvb.org/petition/
----------------------------------------------------------------------------
"Rick Rothstein [MVP - Visual Basic]" <rickNOSPAMnews@NOSPAMcomcast.net>
wrote in message news:%237swRU$$FHA.3136@TK2MSFTNGP15.phx.gbl...
:> 3) use a constant like:
: > Private Const Quot = """"
:
: Just out of curiosity, why wouldn't you go for the extra letter and make
: that
:
: Private Const Quote = """"
:
: instead?
:
: Rick
:
:
| |
| Rick Rothstein [MVP - Visual Basic] 2005-12-14, 3:55 am |
| > Personally, in the couple of apps I've had to do this
> in when working with converting HTML I use just a
> Const q = .... Saves typing and being short keeps
> more of the long and complicated HTML lines in view.
My personal preference is to gang the two quote marks together; but, since
he used a constant definition, I was just wondering why he stopped one
letter short of making the full word.
Rick
| |
| J French 2005-12-14, 3:55 am |
| On Tue, 13 Dec 2005 13:02:40 -0000, "Dave" <nobody@nowhere.com> wrote:
>
>"J French" <erewhon@nowhere.uk> wrote in message
>news:439eb124.351137497@news.btopenworld.com...
>What does "4" + 5 give you?
>9 or 45
>
>With + you have no way to tell, with & you know what it'll do. Obviously one
>shouldn't mix types like in that example but to avoid ambiguity one should
>use the correct syntax. VB allows the use of + just for compatability with
>old code.
To be honest, S$ = T$ + N% should give a type mismatch
- I detest VB's 'intelligent' guesswork
| |
| J French 2005-12-14, 3:55 am |
| On Tue, 13 Dec 2005 09:13:42 -0800, "Karl E. Peterson" <karl@mvps.org>
wrote:
>J French wrote:
>
>Why, *how else* might they have rolled out ETC in VB4, without it???
ETC ?
You've lost me Karl, could you explain
(BTW I've just ported your crafty ForceFore to Delphi - with credit of
course)
| |
|
|
"J French" <erewhon@nowhere.uk> wrote in message
news:439fe5c6.430159250@news.btopenworld.com...
> On Tue, 13 Dec 2005 13:02:40 -0000, "Dave" <nobody@nowhere.com> wrote:
>
>
> To be honest, S$ = T$ + N% should give a type mismatch
> - I detest VB's 'intelligent' guesswork
Well if you "detest VB's 'intelligent' guesswork" use the correct syntax
then it wont have to guess what you mean.
What you use in your own code is of course up to you, but when helping
others out one should always "do it by the book" and definately avoid
obsolete syntax.
Best Regards
Dave O.
| |
| J French 2005-12-14, 7:55 am |
| On Wed, 14 Dec 2005 09:55:33 -0000, "Dave" <nobody@nowhere.com> wrote:
<snip>
[color=darkred]
>Well if you "detest VB's 'intelligent' guesswork" use the correct syntax
>then it wont have to guess what you mean.
You mean apply sticking plaster onto newly introduced faults ?
>What you use in your own code is of course up to you, but when helping
>others out one should always "do it by the book" and definately avoid
>obsolete syntax.
Depends on the 'book'
If one followed MS's edicts then no more INI files
- heck I would have to /recommend/ using the FSO
Here is a 'definative' example from Setup1.exe (basCommon.bas)
- how about this for a lulu way of checking a directory exists ?
Public Function DirExists(ByVal strDirName As String) As Integer
Const strWILDCARD$ = "*.*"
Dim strDummy As String
On Error Resume Next
AddDirSep strDirName
strDummy = Dir$(strDirName & strWILDCARD, vbDirectory)
DirExists = Not (strDummy = gstrNULL)
Err = 0
End Function
Use of Dir$() like this is lethal
- and just look at the confusion between Boolean and Integers
| |
|
|
"J French" <erewhon@nowhere.uk> wrote in message
news:439ffce5.436079813@news.btopenworld.com...
> On Wed, 14 Dec 2005 09:55:33 -0000, "Dave" <nobody@nowhere.com> wrote:
> <snip>
>
>
>
> You mean apply sticking plaster onto newly introduced faults ?
>
>
> Depends on the 'book'
>
> If one followed MS's edicts then no more INI files
> - heck I would have to /recommend/ using the FSO
>
> Here is a 'definative' example from Setup1.exe (basCommon.bas)
> - how about this for a lulu way of checking a directory exists ?
>
> Public Function DirExists(ByVal strDirName As String) As Integer
> Const strWILDCARD$ = "*.*"
>
> Dim strDummy As String
>
> On Error Resume Next
>
> AddDirSep strDirName
> strDummy = Dir$(strDirName & strWILDCARD, vbDirectory)
> DirExists = Not (strDummy = gstrNULL)
>
> Err = 0
> End Function
>
> Use of Dir$() like this is lethal
> - and just look at the confusion between Boolean and Integers
Fair enough that example is rubbish.
What I am saying is that if you illustrate examples with the + operator and
then new users go off and use it in their own programs without having the
depth of knowledge that you have, they are going to encounter unexpected
problems which they will have great difficulty in finding the cause. If
however they only use the & operator then they will never get that
particular problem.
Best Regards
Dave. O.
| |
| Howard Kaikow 2005-12-14, 6:57 pm |
| "Rick Rothstein [MVP - Visual Basic]" <rickNOSPAMnews@NOSPAMcomcast.net>
wrote in message news:uc22fUGAGHA.216@TK2MSFTNGP15.phx.gbl...
>
> My personal preference is to gang the two quote marks together; but, since
> he used a constant definition, I was just wondering why he stopped one
> letter short of making the full word.
>
> Rick
Perhaps, saving the vowel for use on Wheel of Fortune?
| |
| Stefan Berglund 2005-12-14, 6:57 pm |
| On Wed, 14 Dec 2005 13:50:46 -0000, "Dave" <nobody@nowhere.com> wrote:
in <OnYnjVLAGHA.1600@TK2MSFTNGP11.phx.gbl>
>
>"J French" <erewhon@nowhere.uk> wrote in message
>news:439ffce5.436079813@news.btopenworld.com...
>
>Fair enough that example is rubbish.
>
>What I am saying is that if you illustrate examples with the + operator and
>then new users go off and use it in their own programs without having the
>depth of knowledge that you have, they are going to encounter unexpected
>problems which they will have great difficulty in finding the cause. If
>however they only use the & operator then they will never get that
>particular problem.
>
>Best Regards
>Dave. O.
I think your argument re ~new users~ is moot.
---
Stefan Berglund
| |
| Stefan Berglund 2005-12-14, 6:57 pm |
| On Wed, 14 Dec 2005 09:34:14 +0000 (UTC), erewhon@nowhere.uk (J French) wrote:
in <439fe66a.430323287@news.btopenworld.com>
>On Tue, 13 Dec 2005 09:13:42 -0800, "Karl E. Peterson" <karl@mvps.org>
>wrote:
>
>
>ETC ?
>
>You've lost me Karl, could you explain
>(BTW I've just ported your crafty ForceFore to Delphi - with credit of
>course)
A guess would be edit then continue but I'm not an expert on microsoft history.
---
Stefan Berglund
| |
| Bob Butler 2005-12-14, 6:57 pm |
| "Stefan Berglund" <keepit@in.thegroups> wrote in message
news:oqo0q1pubv2epsjemj623eiob939r7f208@
4ax.com
> On Wed, 14 Dec 2005 09:34:14 +0000 (UTC), erewhon@nowhere.uk (J
> French) wrote: in <439fe66a.430323287@news.btopenworld.com>
>
>
> A guess would be edit then continue but I'm not an expert on
> microsoft history.
Evil Type Coercion
--
Reply to the group so all can participate
VB.Net: "Fool me once..."
| |
| Bob Butler 2005-12-14, 6:57 pm |
| "Stefan Berglund" <keepit@in.thegroups> wrote in message
news:lmo0q1tl53l8asdu9ft9abuuqviv5b7ja4@
4ax.com
> I think your argument re ~new users~ is moot.
We've had a few new users show up in the last couple of w s
--
Reply to the group so all can participate
VB.Net: "Fool me once..."
| |
| Karl E. Peterson 2005-12-14, 6:57 pm |
| J French wrote:
> "Karl E. Peterson" <karl@mvps.org> wrote:
>
>
> ETC ?
>
> You've lost me Karl, could you explain
Sorry... Shoulda used the <sarcasm> tags, there.
Yeah, Bob nailed it -- Evil Type Coercion. First introduced at VB4. You
knew what I was talking about, only you didn't know you knew. <g> In
another message, you said:
> To be honest, S$ = T$ + N% should give a type mismatch
> - I detest VB's 'intelligent' guesswork
Which, of course, is exactly what *every* version of MSBasic did prior to
VB4. I think I first wrote about it in an article called "Coercion
Aversion":
http://vb.mvps.org/articles/pt199511.pdf
> (BTW I've just ported your crafty ForceFore to Delphi - with credit of
> course)
Kewl. :-)
--
Working without a .NET?
http://classicvb.org/
| |
| Stefan Berglund 2005-12-14, 6:57 pm |
| On Wed, 14 Dec 2005 10:32:28 -0800, "Bob Butler" <tiredofit@nospam.com> wrote:
in <ehzr#yNAGHA.3984@TK2MSFTNGP14.phx.gbl>
>"Stefan Berglund" <keepit@in.thegroups> wrote in message
> news:lmo0q1tl53l8asdu9ft9abuuqviv5b7ja4@
4ax.com
>
>We've had a few new users show up in the last couple of ws
Yes, and I'm of the opinion that in the interests of full disclosure, they
should be made aware of the fact that their vendor could care less about their
software assets and further that they should consider every vendor other than
microsoft.
I know I'm not the only person here who feels this way, but I just can't help
feeling  . I'd have no problem at all believing that they probably had
already decided on the future of VB way back in 1999, but continued to market it
anyway.
There's a big world out there, and in spite of what microsoft marketing and
ballmer's outright lies would have you believe, microsoft doesn't own it all.
For a bit of an eye-opener read this little bit of propaganda first:
http://download.microsoft.com/downl...YankeePart1.pdf
You might also want to look at Part 2 which is more recent.
Then have a look here:
http://www.e-dynamics.be/docs/linux..._comparison.pdf
In particular, note how and where the author of the Yankee Group effort sourced
her respondents and the nature of the business that her company performs.
ballmer's email is comical.
---
Stefan Berglund
| |
| Bob Butler 2005-12-14, 6:57 pm |
| "Stefan Berglund" <keepit@in.thegroups> wrote in message
news:vvr0q1ttps4nltalgrkrglh95ao30cd121@
4ax.com
> On Wed, 14 Dec 2005 10:32:28 -0800, "Bob Butler"
> <tiredofit@nospam.com> wrote: in
> <ehzr#yNAGHA.3984@TK2MSFTNGP14.phx.gbl>
>
>
> Yes, and I'm of the opinion that in the interests of full disclosure,
> they should be made aware of the fact that their vendor could care
> less about their software assets and further that they should
> consider every vendor other than microsoft.
No argument from me on that one.
> I know I'm not the only person here who feels this way, but I just
> can't help feeling . I'd have no problem at all believing that
> they probably had already decided on the future of VB way back in
> 1999, but continued to market it anyway.
Or that one either. MS screwed over their VB users big time and I doubt
I'll ever trust them again.
OTOH, there are VB newbies and the language is still viable, at least for
the short term.
--
Reply to the group so all can participate
VB.Net: "Fool me once..."
| |
| Stefan Berglund 2005-12-15, 3:55 am |
| On Wed, 14 Dec 2005 11:54:08 -0800, "Bob Butler" <tiredofit@nospam.com> wrote:
in <#HnjngOAGHA.3436@TK2MSFTNGP10.phx.gbl>
>"Stefan Berglund" <keepit@in.thegroups> wrote in message
> news:vvr0q1ttps4nltalgrkrglh95ao30cd121@
4ax.com
>
>No argument from me on that one.
>
>
>Or that one either. MS screwed over their VB users big time and I doubt
>I'll ever trust them again.
>
>OTOH, there are VB newbies and the language is still viable, at least for
>the short term.
I feel the same way and I won't stop using VB until it won't run anymore, but I
also feel it's important enough that others don't make the same mistake and put
their trust in microsoft where it's not only not valued, but it's trashed and
then rubbed repeatedly in their faces.
---
Stefan Berglund
| |
| Kevin Provance 2005-12-15, 3:55 am |
| > Why, *how else* might they have rolled out ETC in VB4, without it???
LMAO!
You just love picking on VB 4. Clearly, it's the black sheep of the family.
<g>
- Kev
| |
| J French 2005-12-15, 7:55 am |
| On Wed, 14 Dec 2005 10:56:01 -0800, "Karl E. Peterson" <karl@mvps.org>
wrote:
<snip>
[color=darkred]
[color=darkred]
>Sorry... Shoulda used the <sarcasm> tags, there.
>Yeah, Bob nailed it -- Evil Type Coercion. First introduced at VB4. You
>knew what I was talking about, only you didn't know you knew. <g> In
>another message, you said:
[color=darkred]
>Which, of course, is exactly what *every* version of MSBasic did prior to
>VB4. I think I first wrote about it in an article called "Coercion
>Aversion":
Ah, thanks - my first VB was VB4 (I hated it)
- before that many BASICs - that behaved sensibly
>http://vb.mvps.org/articles/pt199511.pdf
[color=darkred]
>Kewl. :-)
A seriously smart routine - well worth broadcasting
| |
| J French 2005-12-15, 7:55 am |
| On Thu, 15 Dec 2005 01:09:30 -0500, "Kevin Provance"
<casey@tpasoft.com> wrote:
>
>LMAO!
>
>You just love picking on VB 4. Clearly, it's the black sheep of the family.
><g>
Gawd - it was horrible
- I could find no advantages to counter its drawbacks
| |
| Karl E. Peterson 2005-12-15, 6:55 pm |
| Kevin Provance wrote:
>
> LMAO!
>
> You just love picking on VB 4. Clearly, it's the black sheep of the
> family. <g>
I actually had a lot of fun with VB4, despite, well, despite it all...
In retrospect, it was truly the beginning of the end. We all were put on
fair notice with that release. Trust is a weird thing. "They couldn't be
*that* stupid!", we muttered. Of course they weren't. They had a plan.
:-(
--
Working without a .NET?
http://classicvb.org/
| |
| Bob Butler 2005-12-15, 6:55 pm |
| "Karl E. Peterson" <karl@mvps.org> wrote in message
news:%23Z6GZ2ZAGHA.1312@TK2MSFTNGP09.phx.gbl
> I actually had a lot of fun with VB4, despite, well, despite it all...
>
> In retrospect, it was truly the beginning of the end. We all were
> put on fair notice with that release. Trust is a weird thing. "They
> couldn't be *that* stupid!", we muttered. Of course they weren't.
> They had a plan. :-(
Methinks thou art giving them too much credit. Never ascribe to malice that
which is adequately explained by ignorance and stupidity! <g>
--
Reply to the group so all can participate
VB.Net: "Fool me once..."
| |
| Karl E. Peterson 2005-12-15, 6:55 pm |
| Bob Butler wrote:
> "Karl E. Peterson" <karl@mvps.org> wrote:
>
> Methinks thou art giving them too much credit. Never ascribe to
> malice that which is adequately explained by ignorance and stupidity!
> <g>
I keep telling myself that, in their case, yes. <g>
And to be sure, I'm not saying I think they knew full-well what they were
doing. But remember that VB4 was the first to offer an "Enterprise
Edition." That, really, was the problem. Going after the enterprise, and
abandoning the little guy. It was a total shift in corporate direction,
brought about I suspect by the arrogance of having achieved monopoly
mindshare in the trenches.
--
Working without a .NET?
http://classicvb.org/
| |
| Stefan Berglund 2005-12-15, 6:55 pm |
| On Thu, 15 Dec 2005 09:52:52 -0800, "Karl E. Peterson" <karl@mvps.org> wrote:
in <#KHBgBaAGHA.916@TK2MSFTNGP10.phx.gbl>
>Bob Butler wrote:
>
>I keep telling myself that, in their case, yes. <g>
>
>And to be sure, I'm not saying I think they knew full-well what they were
>doing. But remember that VB4 was the first to offer an "Enterprise
>Edition." That, really, was the problem. Going after the enterprise, and
>abandoning the little guy. It was a total shift in corporate direction,
>brought about I suspect by the arrogance of having achieved monopoly
>mindshare in the trenches.
Unfortunately, that makes an awful lot of sense.
---
Stefan Berglund
| |
| J French 2005-12-16, 3:55 am |
| On Thu, 15 Dec 2005 09:32:59 -0800, "Karl E. Peterson" <karl@mvps.org>
wrote:
>Kevin Provance wrote:
[color=darkred]
>I actually had a lot of fun with VB4, despite, well, despite it all...
I hated it, I was continually re-writing the same visual code as it
did not have UserControls
- VB5 was a breath of fresh air
>In retrospect, it was truly the beginning of the end. We all were put on
>fair notice with that release. Trust is a weird thing. "They couldn't be
>*that* stupid!", we muttered. Of course they weren't. They had a plan.
>:-(
>--
>Working without a .NET?
>http://classicvb.org/
>
>
| |
| J French 2005-12-16, 3:55 am |
| On Thu, 15 Dec 2005 09:41:28 -0800, "Bob Butler"
<tiredofit@nospam.com> wrote:
>"Karl E. Peterson" <karl@mvps.org> wrote in message
>news:%23Z6GZ2ZAGHA.1312@TK2MSFTNGP09.phx.gbl
[color=darkred]
>Methinks thou art giving them too much credit. Never ascribe to malice that
>which is adequately explained by ignorance and stupidity! <g>
Actually I used to follow that principle, but in recent years I have
discovered that malice and stupidity often go hand in hand
- generally the malice comes from people trying to cover up a mistake
|
|
|
|
|