Prev: OleDB Select Top statement not returning data??
Next: CLSID Error; VB6/SP6
From: Kevin Provance on 14 Jul 2010 11:22

"ralph" <nt_consulting64(a)yahoo.net> wrote in message
news:ea8r36tjpfea8apq46ph40ob234irfk2fa(a)4ax.com...

: In the future, if you don't have direct knowledge of a problem, it
: would be wise to stem your desire to defend .Nxt, and take time to at
: least read the OP carefully and do a little research before
: responding.

Never underestimate the respect you command, brother. Had I made this
statement, clementine, skelton and the rest of the evangelicals would have
swarmed to welcome me into their ranks, using the "six degrees of
separation" theory to tie me to their cause. <g>


--
Customer Hatred Knows No Bounds at MSFT
Free usenet access at http://www.eternal-september.org
ClassicVB Users Regroup! comp.lang.basic.visual.misc

Bawwk! Paulie want a dingleball, bawwk!

From: Cor on 14 Jul 2010 13:37
Interesting answer but what is the sense of your message beside some
trolling?

The only true part I've read is that a piece I wrote was gibberish, which is
true.

In fact that gibberish has to be written with an Uppercase, I've already
more times written here, that it is my often used dialect of English.

For the rest I saw only statements like that other person does who only send
troll messages to this newsgroup.

Cor


"ralph" <nt_consulting64(a)yahoo.net> wrote in message
news:ea8r36tjpfea8apq46ph40ob234irfk2fa(a)4ax.com...
> On Wed, 14 Jul 2010 11:09:47 +0200, "Cor Ligthert[MVP]"
> <Notmyfirstname(a)planet.nl> wrote:
>
>>The chance that it is because of a .Net update is less than 0,1%. The VB6
>>runtime uses nowhere the .Net framework.
>>
>
> Interesting observation, but has nothing to do with the OP's question.
> Note: Many applications/programs are having this problem - at this
> time it doesn't appear it is isolated to only products created by VB6.
>
>>Is there no chance that you installed another update (by instance a
>>security
>>one) which has affected that.
>>
>
> According to the various postings, it is this one Update that is
> causing problems.
>
> Also since several people have reported that performing the update
> directly from another source and not via Windows Updater "fixes" the
> problem, strongly suggests that it is 'How' the update is applied and
> not 'What' that is causing the problem.
>
>>Or have you so few memory that the Net updates have affected the memory
>>load
>>of your computer, which can then become of course from every update?
>>
>
> That is gibberish.
>
> In the future, if you don't have direct knowledge of a problem, it
> would be wise to stem your desire to defend .Nxt, and take time to at
> least read the OP carefully and do a little research before
> responding.
>
> -ralph
>
From: Kevin Provance on 14 Jul 2010 14:04

"Cor" <Notmyfirstname(a)planet.nl> wrote in message
news:%23N%23BIt3ILHA.4496(a)TK2MSFTNGP02.phx.gbl...
: Interesting answer but what is the sense of your message beside some
: trolling?

Since it was you who started the trolling, this is a laughable. A troll
accusing a long standing member of this community of being a troll...LMAO!
You're an idiot Cory. Go away.

: In fact that gibberish has to be written with an Uppercase, I've already
: more times written here, that it is my often used dialect of English.

You've already proven multiple times you can't write English worth a damn.
You know how to remedy that? Don't post here at all. Problem solved.
Since you don't use VB6 and are nothing more than a NxT cheerleader, you
have nothing valid to contribute anyway.

: For the rest I saw only statements like that other person does who only
send
: troll messages to this newsgroup.

Everytime you post, it's a troll message. You have no argument. Pick up a
rosetta-stone CD and learn English the right way, then come back. Or don't
and don't come back at all. You don't get dingleballs after all.


--
Customer Hatred Knows No Bounds at MSFT
Free usenet access at http://www.eternal-september.org
ClassicVB Users Regroup! comp.lang.basic.visual.misc

Bawwk! Paulie want a dingleball, bawwk!
Cory me, want me too for one in fact

From: gr on 14 Jul 2010 22:40
Nope, it's not that I don't have enough memory...it's multiple
machines.

It could possibly be another update, but I assumed that it was
the .net ones only b/c it affected our accounting system (Sage) and
when doing my google research it has affected Quickbooks also. It's
the exact same message and it only occurs when we exit the VB
program. (As a clarification, it is only 1 VB app on our computers,
not "many" programs. The "many" I was referring to was the Sage and
QB issues I researched)

Thanks for the help so far people. I'll start removing KBs and see if
I can isolate it to one specific one.

Guy



On Jul 14, 7:08 am, ralph <nt_consultin...(a)yahoo.net> wrote:
> On Wed, 14 Jul 2010 11:09:47 +0200, "Cor Ligthert[MVP]"
>
> <Notmyfirstn...(a)planet.nl> wrote:
> >The chance that it is because of a .Net update is less than 0,1%. The VB6
> >runtime uses nowhere the .Net framework.
>
> Interesting observation, but has nothing to do with the OP's question.
> Note: Many applications/programs are having this problem - at this
> time it doesn't appear it is isolated to only products created by VB6.
>
> >Is there no chance that you installed another update (by instance a security
> >one) which has affected that.
>
> According to the various postings, it is this one Update that is
> causing problems.
>
> Also since several people have reported that performing the update
> directly from another source and not via Windows Updater "fixes" the
> problem, strongly suggests that it is 'How' the update is applied and
> not 'What' that is causing the problem.
>
> >Or have you so few memory that the Net updates have affected the memory load
> >of your computer, which can then become of course from every update?
>
> That is gibberish.
>
> In the future, if you don't have direct knowledge of a problem, it
> would be wise to stem your desire to defend .Nxt, and take time to at
> least read the OP carefully and do a little research before
> responding.
>
> -ralph

From: Cor on 15 Jul 2010 02:52
Hi,

Maybe does it help if you place something here

http://Connect.Microsoft.com

In your case I would tell that it is about a non Net exe. Why tell it is VB6
like you told it, it can be any exe.

Cor

"gr" <guyiniowa(a)gmail.com> wrote in message
news:6632c82b-e92a-4c7f-8454-501327cda01b(a)j8g2000yqd.googlegroups.com...
> Nope, it's not that I don't have enough memory...it's multiple
> machines.
>
> It could possibly be another update, but I assumed that it was
> the .net ones only b/c it affected our accounting system (Sage) and
> when doing my google research it has affected Quickbooks also. It's
> the exact same message and it only occurs when we exit the VB
> program. (As a clarification, it is only 1 VB app on our computers,
> not "many" programs. The "many" I was referring to was the Sage and
> QB issues I researched)
>
> Thanks for the help so far people. I'll start removing KBs and see if
> I can isolate it to one specific one.
>
> Guy
>
>
>
> On Jul 14, 7:08 am, ralph <nt_consultin...(a)yahoo.net> wrote:
>> On Wed, 14 Jul 2010 11:09:47 +0200, "Cor Ligthert[MVP]"
>>
>> <Notmyfirstn...(a)planet.nl> wrote:
>> >The chance that it is because of a .Net update is less than 0,1%. The
>> >VB6
>> >runtime uses nowhere the .Net framework.
>>
>> Interesting observation, but has nothing to do with the OP's question.
>> Note: Many applications/programs are having this problem - at this
>> time it doesn't appear it is isolated to only products created by VB6.
>>
>> >Is there no chance that you installed another update (by instance a
>> >security
>> >one) which has affected that.
>>
>> According to the various postings, it is this one Update that is
>> causing problems.
>>
>> Also since several people have reported that performing the update
>> directly from another source and not via Windows Updater "fixes" the
>> problem, strongly suggests that it is 'How' the update is applied and
>> not 'What' that is causing the problem.
>>
>> >Or have you so few memory that the Net updates have affected the memory
>> >load
>> >of your computer, which can then become of course from every update?
>>
>> That is gibberish.
>>
>> In the future, if you don't have direct knowledge of a problem, it
>> would be wise to stem your desire to defend .Nxt, and take time to at
>> least read the OP carefully and do a little research before
>> responding.
>>
>> -ralph
>
>
First  |  Prev  | 
Pages: 1 2 3
Prev: OleDB Select Top statement not returning data??
Next: CLSID Error; VB6/SP6