-
Error: dbSQL, dbStoredProc, X.dbStoredProcCmdParams cannot be all blank
Why might I be getting this error whenever I click on the next or bottom button?
-
Error: dbSQL, dbStoredProc, X.dbStoredProcCmdParams cannot be all blank (reply)
this error is a dtection of all the data sources properties are blank...
FK
------------
Rich Paino at 4/25/01 1:14:07 PM
Why might I be getting this error whenever I click on the next or bottom button?
-
Error: dbSQL, dbStoredProc, X.dbStoredProcCmdParams cannot be all blank (reply)
But I have a record collection of more records than are on the screen and I simply hit the "Next" to go to the next 5 records. I know there are more records because I use a dbRecordCount which tells me how many there are. For example I'm showing 18 of 24 records, when I click "Next" I get the error. It doesn't make sense.
------------
Frank Kwong at 4/25/01 3:34:07 PM
this error is a dtection of all the data sources properties are blank...
FK
------------
Rich Paino at 4/25/01 1:14:07 PM
Why might I be getting this error whenever I click on the next or bottom button?
-
Error: dbSQL, dbStoredProc, X.dbStoredProcCmdParams cannot be all blank (reply)
the properties is blank means it is being changed to blank by code.
FK
------------
Rich Paino at 4/25/01 3:50:14 PM
But I have a record collection of more records than are on the screen and I simply hit the "Next" to go to the next 5 records. I know there are more records because I use a dbRecordCount which tells me how many there are. For example I'm showing 18 of 24 records, when I click "Next" I get the error. It doesn't make sense.
------------
Frank Kwong at 4/25/01 3:34:07 PM
this error is a dtection of all the data sources properties are blank...
FK
------------
Rich Paino at 4/25/01 1:14:07 PM
Why might I be getting this error whenever I click on the next or bottom button?
-
Error: dbSQL, dbStoredProc, X.dbStoredProcCmdParams cannot be all blank (reply)
I don't believe that's right Frank. Here is the code:
Select Case varQueryName
Case "Checked By..."
MyDb.dbSQL = "SELECT * FROM [Customer Info] " _
& "WHERE ((([Customer Info].Checkedby)='" & varCheckedBy & "')"
(Other cases)
End Select
That's it. then I just execute the MyDb.aspDBEP
------------
Frank Kwong at 4/25/01 9:12:09 PM
the properties is blank means it is being changed to blank by code.
FK
------------
Rich Paino at 4/25/01 3:50:14 PM
But I have a record collection of more records than are on the screen and I simply hit the "Next" to go to the next 5 records. I know there are more records because I use a dbRecordCount which tells me how many there are. For example I'm showing 18 of 24 records, when I click "Next" I get the error. It doesn't make sense.
------------
Frank Kwong at 4/25/01 3:34:07 PM
this error is a dtection of all the data sources properties are blank...
FK
------------
Rich Paino at 4/25/01 1:14:07 PM
Why might I be getting this error whenever I click on the next or bottom button?
-
Error: dbSQL, dbStoredProc, X.dbStoredProcCmdParams cannot be all blank (reply)
I'm getting the same error. I have an if/then statement that sets the SQL and I am using a UNION statement in the SQL as well. I get this error if I click the next button or if I try to sort by one of the headers.
------------
Rich Paino at 4/25/01 1:14:07 PM
Why might I be getting this error whenever I click on the next or bottom button?
-
Error: dbSQL, dbStoredProc, X.dbStoredProcCmdParams cannot be all blank (reply)
Where does varQueryName comes from ? place you cursor on the "next" button and see whether this variable there ready to be emitted to the URL. If not then you have to retain this variable using dbOptions="KeepUserQueryString=true" if it is a new activation or use session variable to retain this variable. Otherwise, the variable will be gone when you hit "next". Try this ->
..
..
S="SELECT * FROM [Customer Info] & "WHERE ((([Customer Info].Checkedby)='" & varCheckedBy & "')"
resonse.write "Constructed SQL = " & s
X.dbSQL=s
..
..
MyDb.aspDBEP
what is "s" ?
Also try this .....
varCheckedBy=value
varQueryName=value
session("VQN"=varQueryName
session("VCB"=carCheckedBY
Select Case session("VQN"
Case "Checked By..."
MyDb.dbSQL = "SELECT * FROM [Customer Info] " _
& "WHERE ((([Customer Info].Checkedby)='" & session("VCB" & "')"
(Other cases)
End Select
FK
------------
Rich Paino at 5/1/01 11:01:47 AM
I don't believe that's right Frank. Here is the code:
Select Case varQueryName
Case "Checked By..."
MyDb.dbSQL = "SELECT * FROM [Customer Info] " _
& "WHERE ((([Customer Info].Checkedby)='" & varCheckedBy & "')"
(Other cases)
End Select
That's it. then I just execute the MyDb.aspDBEP
------------
Frank Kwong at 4/25/01 9:12:09 PM
the properties is blank means it is being changed to blank by code.
FK
------------
Rich Paino at 4/25/01 3:50:14 PM
But I have a record collection of more records than are on the screen and I simply hit the "Next" to go to the next 5 records. I know there are more records because I use a dbRecordCount which tells me how many there are. For example I'm showing 18 of 24 records, when I click "Next" I get the error. It doesn't make sense.
------------
Frank Kwong at 4/25/01 3:34:07 PM
this error is a dtection of all the data sources properties are blank...
FK
------------
Rich Paino at 4/25/01 1:14:07 PM
Why might I be getting this error whenever I click on the next or bottom button?
-
Rich! Did you ever get this fixed?
If so, I am wondering how. Frank, I am having this same problem. The strange thing is...when I run it, I have the session("mySQL_Unit#" displayed and it shows the construct! Yet on the very same screen, it says the the dbSQL is empty! How can this be?!?
------------
Frank Kwong at 5/2/01 12:38:28 AM
Where does varQueryName comes from ? place you cursor on the "next" button and see whether this variable there ready to be emitted to the URL. If not then you have to retain this variable using dbOptions="KeepUserQueryString=true" if it is a new activation or use session variable to retain this variable. Otherwise, the variable will be gone when you hit "next". Try this ->
..
..
S="SELECT * FROM [Customer Info] & "WHERE ((([Customer Info].Checkedby)='" & varCheckedBy & "')"
resonse.write "Constructed SQL = " & s
X.dbSQL=s
..
..
MyDb.aspDBEP
what is "s" ?
Also try this .....
varCheckedBy=value
varQueryName=value
session("VQN"=varQueryName
session("VCB"=carCheckedBY
Select Case session("VQN"
Case "Checked By..."
MyDb.dbSQL = "SELECT * FROM [Customer Info] " _
& "WHERE ((([Customer Info].Checkedby)='" & session("VCB" & "')"
(Other cases)
End Select
FK
------------
Rich Paino at 5/1/01 11:01:47 AM
I don't believe that's right Frank. Here is the code:
Select Case varQueryName
Case "Checked By..."
MyDb.dbSQL = "SELECT * FROM [Customer Info] " _
& "WHERE ((([Customer Info].Checkedby)='" & varCheckedBy & "')"
(Other cases)
End Select
That's it. then I just execute the MyDb.aspDBEP
------------
Frank Kwong at 4/25/01 9:12:09 PM
the properties is blank means it is being changed to blank by code.
FK
------------
Rich Paino at 4/25/01 3:50:14 PM
But I have a record collection of more records than are on the screen and I simply hit the "Next" to go to the next 5 records. I know there are more records because I use a dbRecordCount which tells me how many there are. For example I'm showing 18 of 24 records, when I click "Next" I get the error. It doesn't make sense.
------------
Frank Kwong at 4/25/01 3:34:07 PM
this error is a dtection of all the data sources properties are blank...
FK
------------
Rich Paino at 4/25/01 1:14:07 PM
Why might I be getting this error whenever I click on the next or bottom button?
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
|