Velocity Reviews - Computer Hardware Reviews

Velocity Reviews > Newsgroups > Programming > ASP .Net > Please solve this.

Reply
Thread Tools

Please solve this.

 
 
bbawa1@yahoo.com
Guest
Posts: n/a
 
      06-21-2007
It says invalid expression term &&

protected void GridView1_RowDataBound(object sender,
GridViewRowEventArgs e)
{

if
((Convert.ToInt32(e.Row.Cells[2].Text)>=15))&&(Convert.ToInt32(e.Row.Cells[2].Text)>=17);
{

e.Row.Cells[0].CssClass = "sdgStatusOrange";

}

It says invalid expression term &&

 
Reply With Quote
 
 
 
 
Turkbear
Guest
Posts: n/a
 
      06-21-2007
On Thu, 21 Jun 2007 13:19:41 -0700, http://www.velocityreviews.com/forums/(E-Mail Removed) wrote:

> It says invalid expression term &&
>
> protected void GridView1_RowDataBound(object sender,
>GridViewRowEventArgs e)
> {
>
>if
>((Convert.ToInt32(e.Row.Cells[2].Text)>=15))&&(Convert.ToInt32(e.Row.Cells[2].Text)>=17);
>{
>
> e.Row.Cells[0].CssClass = "sdgStatusOrange";
>
>}
>
>It says invalid expression term &&


Check the parens ( maybe):
if
((Convert.ToInt32(e.Row.Cells[2].Text)>=15)&& (Convert.ToInt32(e.Row.Cells[2].Text)>=17)) ;
{

e.Row.Cells[0].CssClass = "sdgStatusOrange";
}
 
Reply With Quote
 
 
 
 
Mark Rae
Guest
Posts: n/a
 
      06-21-2007
<(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ps.com...
> It says invalid expression term &&
>
> protected void GridView1_RowDataBound(object sender,
> GridViewRowEventArgs e)
> {
>
> if
> ((Convert.ToInt32(e.Row.Cells[2].Text)>=15))&&(Convert.ToInt32(e.Row.Cells[2].Text)>=17);
> {
>
> e.Row.Cells[0].CssClass = "sdgStatusOrange";
>
> }
>
> It says invalid expression term &&


You've got your parentheses slightly confused:

if((Convert.ToInt32(e.Row.Cells[2].Text)>=15)&&(Convert.ToInt32(e.Row.Cells[2].Text)>=17))



--
http://www.markrae.net

 
Reply With Quote
 
Juan T. Llibre
Guest
Posts: n/a
 
      06-21-2007
re:
((Convert.ToInt32(e.Row.Cells[2].Text)>=15))&&(Convert.ToInt32(e.Row.Cells[2].Text)>=17);

You need to use the "regular" AND operator.

Try :

((Convert.ToInt32(e.Row.Cells[2].Text)>=15))&(Convert.ToInt32(e.Row.Cells[2].Text)>=17);

If you use && and e.Row.Cells[2].Text)>=15 is false, e.Row.Cells[2].Text)>=17
is not evaluated (because the result of the AND operation is false no matter what the
value of e.Row.Cells[2].Text)>=17 may be).

This is known as "short-circuit" evaluation...but it requires *both* operands to be true.
In your code, that is not alsways the case.






Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en espa˝ol : http://asp.net.do/foros/
======================================
<(E-Mail Removed)> wrote in message news:(E-Mail Removed) ps.com...
> It says invalid expression term &&
>
> protected void GridView1_RowDataBound(object sender,
> GridViewRowEventArgs e)
> {
>
> if
> ((Convert.ToInt32(e.Row.Cells[2].Text)>=15))&&(Convert.ToInt32(e.Row.Cells[2].Text)>=17);
> {
>
> e.Row.Cells[0].CssClass = "sdgStatusOrange";
>
> }
>
> It says invalid expression term &&
>



 
Reply With Quote
 
Juan T. Llibre
Guest
Posts: n/a
 
      06-21-2007
The problem is a bit more than just misplaced parens.
See my just-sent explanation.




Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en espa˝ol : http://asp.net.do/foros/
======================================
"Turkbear" <(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
> On Thu, 21 Jun 2007 13:19:41 -0700, (E-Mail Removed) wrote:
>
>> It says invalid expression term &&
>>
>> protected void GridView1_RowDataBound(object sender,
>>GridViewRowEventArgs e)
>> {
>>
>>if
>>((Convert.ToInt32(e.Row.Cells[2].Text)>=15))&&(Convert.ToInt32(e.Row.Cells[2].Text)>=17);
>>{
>>
>> e.Row.Cells[0].CssClass = "sdgStatusOrange";
>>
>>}
>>
>>It says invalid expression term &&

>
> Check the parens ( maybe):
> if
> ((Convert.ToInt32(e.Row.Cells[2].Text)>=15)&& (Convert.ToInt32(e.Row.Cells[2].Text)>=17)) ;
> {
>
> e.Row.Cells[0].CssClass = "sdgStatusOrange";
> }



 
Reply With Quote
 
=?Utf-8?B?TWlsb3N6IFNrYWxlY2tpIFtNQ0FEXQ==?=
Guest
Posts: n/a
 
      06-21-2007
Hi Juan,

In this case, "invalid expression term &&" is caused definitely by misplaced
parentheses, because it is a compiler message (evaluation would be done
at the runtime). Second, bitwise and & operator will give the same result
(apart from the fact short-circuit is not apllicable) because true & true =
true, false & true = false, false & false = false. Therefore, it should be
corrected to:

if (
(Convert.ToInt32(e.Row.Cells[2].Text) >= 15) &&
(Convert.ToInt32(e.Row.Cells[2].Text) >= 17))
{
e.Row.Cells[0].CssClass = "sdgStatusOrange";
}

Best regards
--
Milosz


"Juan T. Llibre" wrote:

> re:
> ((Convert.ToInt32(e.Row.Cells[2].Text)>=15))&&(Convert.ToInt32(e.Row.Cells[2].Text)>=17);
>
> You need to use the "regular" AND operator.
>
> Try :
>
> ((Convert.ToInt32(e.Row.Cells[2].Text)>=15))&(Convert.ToInt32(e.Row.Cells[2].Text)>=17);
>
> If you use && and e.Row.Cells[2].Text)>=15 is false, e.Row.Cells[2].Text)>=17
> is not evaluated (because the result of the AND operation is false no matter what the
> value of e.Row.Cells[2].Text)>=17 may be).
>
> This is known as "short-circuit" evaluation...but it requires *both* operands to be true.
> In your code, that is not alsways the case.
>
>
>
>
>
>
> Juan T. Llibre, asp.net MVP
> asp.net faq : http://asp.net.do/faq/
> foros de asp.net, en espa├▒ol : http://asp.net.do/foros/
> ======================================
> <(E-Mail Removed)> wrote in message news:(E-Mail Removed) ps.com...
> > It says invalid expression term &&
> >
> > protected void GridView1_RowDataBound(object sender,
> > GridViewRowEventArgs e)
> > {
> >
> > if
> > ((Convert.ToInt32(e.Row.Cells[2].Text)>=15))&&(Convert.ToInt32(e.Row.Cells[2].Text)>=17);
> > {
> >
> > e.Row.Cells[0].CssClass = "sdgStatusOrange";
> >
> > }
> >
> > It says invalid expression term &&
> >

>
>
>

 
Reply With Quote
 
Juan T. Llibre
Guest
Posts: n/a
 
      06-22-2007
Hi, Milosz,

In that case, what happens if Convert.ToInt32(e.Row.Cells[2].Text = 14) ?




Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en espa˝ol : http://asp.net.do/foros/
======================================
"Milosz Skalecki [MCAD]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi Juan,
>
> In this case, "invalid expression term &&" is caused definitely by misplaced
> parentheses, because it is a compiler message (evaluation would be done
> at the runtime). Second, bitwise and & operator will give the same result
> (apart from the fact short-circuit is not apllicable) because true & true =
> true, false & true = false, false & false = false. Therefore, it should be
> corrected to:
>
> if (
> (Convert.ToInt32(e.Row.Cells[2].Text) >= 15) &&
> (Convert.ToInt32(e.Row.Cells[2].Text) >= 17))
> {
> e.Row.Cells[0].CssClass = "sdgStatusOrange";
> }
>
> Best regards
> --
> Milosz
>
>
> "Juan T. Llibre" wrote:
>
>> re:
>> ((Convert.ToInt32(e.Row.Cells[2].Text)>=15))&&(Convert.ToInt32(e.Row.Cells[2].Text)>=17);
>>
>> You need to use the "regular" AND operator.
>>
>> Try :
>>
>> ((Convert.ToInt32(e.Row.Cells[2].Text)>=15))&(Convert.ToInt32(e.Row.Cells[2].Text)>=17);
>>
>> If you use && and e.Row.Cells[2].Text)>=15 is false, e.Row.Cells[2].Text)>=17
>> is not evaluated (because the result of the AND operation is false no matter what the
>> value of e.Row.Cells[2].Text)>=17 may be).
>>
>> This is known as "short-circuit" evaluation...but it requires *both* operands to be true.
>> In your code, that is not alsways the case.
>>
>>
>>
>>
>>
>>
>> Juan T. Llibre, asp.net MVP
>> asp.net faq : http://asp.net.do/faq/
>> foros de asp.net, en espa├▒ol : http://asp.net.do/foros/
>> ======================================
>> <(E-Mail Removed)> wrote in message news:(E-Mail Removed) ps.com...
>> > It says invalid expression term &&
>> >
>> > protected void GridView1_RowDataBound(object sender,
>> > GridViewRowEventArgs e)
>> > {
>> >
>> > if
>> > ((Convert.ToInt32(e.Row.Cells[2].Text)>=15))&&(Convert.ToInt32(e.Row.Cells[2].Text)>=17);
>> > {
>> >
>> > e.Row.Cells[0].CssClass = "sdgStatusOrange";
>> >
>> > }
>> >
>> > It says invalid expression term &&
>> >

>>
>>
>>



 
Reply With Quote
 
=?Utf-8?B?TWlsb3N6IFNrYWxlY2tpIFtNQ0FEXQ==?=
Guest
Posts: n/a
 
      06-22-2007
Good morning Juan

Did you mean if the text in cell equals "14"

if (
(Convert.ToInt32(e.Row.Cells[2].Text) >= 15) &&
(Convert.ToInt32(e.Row.Cells[2].Text) >= 17))
{
e.Row.Cells[0].CssClass = "sdgStatusOrange";
}

then statement inside is not going to be reached, simply because the first
condition is false, and short-circuit evaluation for && operator skips the
second operand. I understand your confusion as I have seen this guy's
previous post, but in this case it was just misplaced parentheses
--
Milosz


"Juan T. Llibre" wrote:

> Hi, Milosz,
>
> In that case, what happens if Convert.ToInt32(e.Row.Cells[2].Text = 14) ?
>
>
>
>
> Juan T. Llibre, asp.net MVP
> asp.net faq : http://asp.net.do/faq/
> foros de asp.net, en espa├▒ol : http://asp.net.do/foros/
> ======================================
> "Milosz Skalecki [MCAD]" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > Hi Juan,
> >
> > In this case, "invalid expression term &&" is caused definitely by misplaced
> > parentheses, because it is a compiler message (evaluation would be done
> > at the runtime). Second, bitwise and & operator will give the same result
> > (apart from the fact short-circuit is not apllicable) because true & true =
> > true, false & true = false, false & false = false. Therefore, it should be
> > corrected to:
> >
> > if (
> > (Convert.ToInt32(e.Row.Cells[2].Text) >= 15) &&
> > (Convert.ToInt32(e.Row.Cells[2].Text) >= 17))
> > {
> > e.Row.Cells[0].CssClass = "sdgStatusOrange";
> > }
> >
> > Best regards
> > --
> > Milosz
> >
> >
> > "Juan T. Llibre" wrote:
> >
> >> re:
> >> ((Convert.ToInt32(e.Row.Cells[2].Text)>=15))&&(Convert.ToInt32(e.Row.Cells[2].Text)>=17);
> >>
> >> You need to use the "regular" AND operator.
> >>
> >> Try :
> >>
> >> ((Convert.ToInt32(e.Row.Cells[2].Text)>=15))&(Convert.ToInt32(e.Row.Cells[2].Text)>=17);
> >>
> >> If you use && and e.Row.Cells[2].Text)>=15 is false, e.Row.Cells[2].Text)>=17
> >> is not evaluated (because the result of the AND operation is false no matter what the
> >> value of e.Row.Cells[2].Text)>=17 may be).
> >>
> >> This is known as "short-circuit" evaluation...but it requires *both* operands to be true.
> >> In your code, that is not alsways the case.
> >>
> >>
> >>
> >>
> >>
> >>
> >> Juan T. Llibre, asp.net MVP
> >> asp.net faq : http://asp.net.do/faq/
> >> foros de asp.net, en español : http://asp.net.do/foros/
> >> ======================================
> >> <(E-Mail Removed)> wrote in message news:(E-Mail Removed) ps.com...
> >> > It says invalid expression term &&
> >> >
> >> > protected void GridView1_RowDataBound(object sender,
> >> > GridViewRowEventArgs e)
> >> > {
> >> >
> >> > if
> >> > ((Convert.ToInt32(e.Row.Cells[2].Text)>=15))&&(Convert.ToInt32(e.Row.Cells[2].Text)>=17);
> >> > {
> >> >
> >> > e.Row.Cells[0].CssClass = "sdgStatusOrange";
> >> >
> >> > }
> >> >
> >> > It says invalid expression term &&
> >> >
> >>
> >>
> >>

>
>
>

 
Reply With Quote
 
Juan T. Llibre
Guest
Posts: n/a
 
      06-22-2007
re:
!> Did you mean if the text in cell equals "14"

Yes.

re:
!> then statement inside is not going to be reached, simply because the first
!> condition is false, and short-circuit evaluation for && operator skips the second operand.

That's exactly what I explained...and that's an undesirable "feature".
That's why he needs to change the operator.

re:
!> I understand your confusion

There's no confusion.

He should change both the parens *and* the operator,
the first as you suggest; the second as I suggest.

Doing that will cover all the bases for him.




Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en espa˝ol : http://asp.net.do/foros/
======================================
"Milosz Skalecki [MCAD]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Good morning Juan
>
> Did you mean if the text in cell equals "14"
>
> if (
> (Convert.ToInt32(e.Row.Cells[2].Text) >= 15) &&
> (Convert.ToInt32(e.Row.Cells[2].Text) >= 17))
> {
> e.Row.Cells[0].CssClass = "sdgStatusOrange";
> }
>
> then statement inside is not going to be reached, simply because the first
> condition is false, and short-circuit evaluation for && operator skips the
> second operand. I understand your confusion as I have seen this guy's
> previous post, but in this case it was just misplaced parentheses
> --
> Milosz
>
>
> "Juan T. Llibre" wrote:
>
>> Hi, Milosz,
>>
>> In that case, what happens if Convert.ToInt32(e.Row.Cells[2].Text = 14) ?
>>
>>
>>
>>
>> Juan T. Llibre, asp.net MVP
>> asp.net faq : http://asp.net.do/faq/
>> foros de asp.net, en espa├▒ol : http://asp.net.do/foros/
>> ======================================
>> "Milosz Skalecki [MCAD]" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>> > Hi Juan,
>> >
>> > In this case, "invalid expression term &&" is caused definitely by misplaced
>> > parentheses, because it is a compiler message (evaluation would be done
>> > at the runtime). Second, bitwise and & operator will give the same result
>> > (apart from the fact short-circuit is not apllicable) because true & true =
>> > true, false & true = false, false & false = false. Therefore, it should be
>> > corrected to:
>> >
>> > if (
>> > (Convert.ToInt32(e.Row.Cells[2].Text) >= 15) &&
>> > (Convert.ToInt32(e.Row.Cells[2].Text) >= 17))
>> > {
>> > e.Row.Cells[0].CssClass = "sdgStatusOrange";
>> > }
>> >
>> > Best regards
>> > --
>> > Milosz
>> >
>> >
>> > "Juan T. Llibre" wrote:
>> >
>> >> re:
>> >> ((Convert.ToInt32(e.Row.Cells[2].Text)>=15))&&(Convert.ToInt32(e.Row.Cells[2].Text)>=17);
>> >>
>> >> You need to use the "regular" AND operator.
>> >>
>> >> Try :
>> >>
>> >> ((Convert.ToInt32(e.Row.Cells[2].Text)>=15))&(Convert.ToInt32(e.Row.Cells[2].Text)>=17);
>> >>
>> >> If you use && and e.Row.Cells[2].Text)>=15 is false, e.Row.Cells[2].Text)>=17
>> >> is not evaluated (because the result of the AND operation is false no matter what the
>> >> value of e.Row.Cells[2].Text)>=17 may be).
>> >>
>> >> This is known as "short-circuit" evaluation...but it requires *both* operands to be true.
>> >> In your code, that is not alsways the case.
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> Juan T. Llibre, asp.net MVP
>> >> asp.net faq : http://asp.net.do/faq/
>> >> foros de asp.net, en español : http://asp.net.do/foros/
>> >> ======================================
>> >> <(E-Mail Removed)> wrote in message
>> >> news:(E-Mail Removed) ps.com...
>> >> > It says invalid expression term &&
>> >> >
>> >> > protected void GridView1_RowDataBound(object sender,
>> >> > GridViewRowEventArgs e)
>> >> > {
>> >> >
>> >> > if
>> >> > ((Convert.ToInt32(e.Row.Cells[2].Text)>=15))&&(Convert.ToInt32(e.Row.Cells[2].Text)>=17);
>> >> > {
>> >> >
>> >> > e.Row.Cells[0].CssClass = "sdgStatusOrange";
>> >> >
>> >> > }
>> >> >
>> >> > It says invalid expression term &&
>> >> >
>> >>
>> >>
>> >>

>>
>>
>>



 
Reply With Quote
 
=?Utf-8?B?TWlsb3N6IFNrYWxlY2tpIFtNQ0FEXQ==?=
Guest
Posts: n/a
 
      06-22-2007
Juan,

Come on, i can't see any logical exlanation in changing && operator to & for
this case . First of all, logically, his "if" statement could be
simplified changed to:
if (Convert.ToInt32(e.Row.Cells[2].Text) >= 17)
{
e.Row.Cells[0].CssClass = "sdgStatusOrange";
}
simply because the only numbers that meet both criteria are >= 17. Second,
if the first operand (Convert.ToInt32(e.Row.Cells[2].Text) >= 15) would
return false, second could not be true (logically). Please also note he used
&& therefore there is not point to test the second operand as you're trying
to point out. Third, it was definitely compiler error (syntax error) which
has nothing to do with runtime evaluation.

Take it easy mate

Best regards
--
Milosz


"Juan T. Llibre" wrote:

> re:
> !> Did you mean if the text in cell equals "14"
>
> Yes.
>
> re:
> !> then statement inside is not going to be reached, simply because the first
> !> condition is false, and short-circuit evaluation for && operator skips the second operand.
>
> That's exactly what I explained...and that's an undesirable "feature".
> That's why he needs to change the operator.
>
> re:
> !> I understand your confusion
>
> There's no confusion.
>
> He should change both the parens *and* the operator,
> the first as you suggest; the second as I suggest.
>
> Doing that will cover all the bases for him.
>
>
>
>
> Juan T. Llibre, asp.net MVP
> asp.net faq : http://asp.net.do/faq/
> foros de asp.net, en espa├▒ol : http://asp.net.do/foros/
> ======================================
> "Milosz Skalecki [MCAD]" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > Good morning Juan
> >
> > Did you mean if the text in cell equals "14"
> >
> > if (
> > (Convert.ToInt32(e.Row.Cells[2].Text) >= 15) &&
> > (Convert.ToInt32(e.Row.Cells[2].Text) >= 17))
> > {
> > e.Row.Cells[0].CssClass = "sdgStatusOrange";
> > }
> >
> > then statement inside is not going to be reached, simply because the first
> > condition is false, and short-circuit evaluation for && operator skips the
> > second operand. I understand your confusion as I have seen this guy's
> > previous post, but in this case it was just misplaced parentheses
> > --
> > Milosz
> >
> >
> > "Juan T. Llibre" wrote:
> >
> >> Hi, Milosz,
> >>
> >> In that case, what happens if Convert.ToInt32(e.Row.Cells[2].Text = 14) ?
> >>
> >>
> >>
> >>
> >> Juan T. Llibre, asp.net MVP
> >> asp.net faq : http://asp.net.do/faq/
> >> foros de asp.net, en español : http://asp.net.do/foros/
> >> ======================================
> >> "Milosz Skalecki [MCAD]" <(E-Mail Removed)> wrote in message
> >> news:(E-Mail Removed)...
> >> > Hi Juan,
> >> >
> >> > In this case, "invalid expression term &&" is caused definitely by misplaced
> >> > parentheses, because it is a compiler message (evaluation would be done
> >> > at the runtime). Second, bitwise and & operator will give the same result
> >> > (apart from the fact short-circuit is not apllicable) because true & true =
> >> > true, false & true = false, false & false = false. Therefore, it should be
> >> > corrected to:
> >> >
> >> > if (
> >> > (Convert.ToInt32(e.Row.Cells[2].Text) >= 15) &&
> >> > (Convert.ToInt32(e.Row.Cells[2].Text) >= 17))
> >> > {
> >> > e.Row.Cells[0].CssClass = "sdgStatusOrange";
> >> > }
> >> >
> >> > Best regards
> >> > --
> >> > Milosz
> >> >
> >> >
> >> > "Juan T. Llibre" wrote:
> >> >
> >> >> re:
> >> >> ((Convert.ToInt32(e.Row.Cells[2].Text)>=15))&&(Convert.ToInt32(e.Row.Cells[2].Text)>=17);
> >> >>
> >> >> You need to use the "regular" AND operator.
> >> >>
> >> >> Try :
> >> >>
> >> >> ((Convert.ToInt32(e.Row.Cells[2].Text)>=15))&(Convert.ToInt32(e.Row.Cells[2].Text)>=17);
> >> >>
> >> >> If you use && and e.Row.Cells[2].Text)>=15 is false, e.Row.Cells[2].Text)>=17
> >> >> is not evaluated (because the result of the AND operation is false no matter what the
> >> >> value of e.Row.Cells[2].Text)>=17 may be).
> >> >>
> >> >> This is known as "short-circuit" evaluation...but it requires *both* operands to be true.
> >> >> In your code, that is not alsways the case.
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> Juan T. Llibre, asp.net MVP
> >> >> asp.net faq : http://asp.net.do/faq/
> >> >> foros de asp.net, en espa├âĂĺ├é┬▒ol : http://asp.net.do/foros/
> >> >> ======================================
> >> >> <(E-Mail Removed)> wrote in message
> >> >> news:(E-Mail Removed) ps.com...
> >> >> > It says invalid expression term &&
> >> >> >
> >> >> > protected void GridView1_RowDataBound(object sender,
> >> >> > GridViewRowEventArgs e)
> >> >> > {
> >> >> >
> >> >> > if
> >> >> > ((Convert.ToInt32(e.Row.Cells[2].Text)>=15))&&(Convert.ToInt32(e.Row.Cells[2].Text)>=17);
> >> >> > {
> >> >> >
> >> >> > e.Row.Cells[0].CssClass = "sdgStatusOrange";
> >> >> >
> >> >> > }
> >> >> >
> >> >> > It says invalid expression term &&
> >> >> >
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>

>
>
>

 
Reply With Quote
 
 
 
Reply

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
An Irritating Thunderbird Newsgroup Problem...Please Solve It! Ann Speakman Firefox 2 03-09-2005 12:08 AM
Can somebody please help me solve DVD Decrytper mystery? LZernov DVD Video 1 01-31-2005 07:25 PM
please solve my problem Toolman Tim Computer Support 17 07-09-2004 03:49 AM
Disappearing OE 5.5 archicve files -- Please help solve puzzle!!!! Jim McLaughlin Computer Support 29 02-11-2004 09:00 PM
please help... ...me learn C++ please please please :) KK C++ 2 10-14-2003 02:08 PM



Advertisments