Re: sql call not working but should!
From: David Browne (meat_at_hotmail.com)
Date: 05/25/04
- Next message: David Browne: "Re: Shared dataset & SyncLock"
- Previous message: Deva: "Why I cannot use two DataSets?"
- In reply to: chris: "sql call not working but should!"
- Next in thread: William Ryan eMVP: "Re: sql call not working but should!"
- Reply: William Ryan eMVP: "Re: sql call not working but should!"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 25 May 2004 13:24:31 -0500
"chris" <anonymous@discussions.microsoft.com> wrote in message
news:C05BF536-840F-4C79-B54A-DF6125A94AE7@microsoft.com...
> I have this login routine that I can't seem to get the Sub loginpartner to
work. There are two login subs on this >page (loginnasba (works) and
loginpartner (does not)). The sql statement for loginpartner has been
confirmed to >work. But it won't allow login, genertating no hasrows
(setting lblpartnerloginfailed.text label on else). If I replace it >with
the Sub loginnasba sql statement, modifying the fields that get populated
from the form accordingly, then login >works! What am I not seeing? I run
the SQL3 statement through my SQl Server 2K and it works! THANX!
This code is impossible to read. Move the procedures to a VB code-behind
module, strip the comments and replace all the SQL string concatenation with
parameter markers and bind the parameters.
If that doesn't fix it, at least it will be more readable.
David
- Next message: David Browne: "Re: Shared dataset & SyncLock"
- Previous message: Deva: "Why I cannot use two DataSets?"
- In reply to: chris: "sql call not working but should!"
- Next in thread: William Ryan eMVP: "Re: sql call not working but should!"
- Reply: William Ryan eMVP: "Re: sql call not working but should!"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
