Unanticipated Results when Executing a SQL stored procedure from Access 2010
I’ve created a pass-through query in Access which executes a stored procedure that searches for a string across all tables in my SQL database. The stored procedure on the SQL server runs as expected with results that show all the tables that contain the value in my search string. However, when I run that same SP using the pass-through query in Access, the Access “view” returns only one table instead of multiple tables that contain my value. I know the Access interface behaves differently than SQL, but I have a form which is bound to the search result of the pass-through query and I need the users to view all of the tables which contain their search string.
tigin44
did you check the privileges that the access connection have when you run the query across the sql server? This may be a privilege problem
ASKER
I'm connecting via trust connection to the SQL server as a domain admin so privileges aren't an issue. There are no error messages and the query executes just fine except it returns only one table.
I don't use stored procedures that return multiple recordsets for this very reason. You can probably get to the other recordsets if you work with the results in code but not when it is bound to a form.
Create a separate sp for each recordset.
Create a separate sp for each recordset.
ASKER
Sorry, I misworded my question and should have said that my form is not bound to the search result, I am using the .Connect and .sql properties in code to list the results in an unbound control, but I think I’m incorrectly using the pass-through query. I will try your approach and let you know how it goes.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Christian,
Thanks for this. I changed my method and decided to not use a pass-through query and just call the SP from SQL using VBA:
Darlyne
Thanks for this. I changed my method and decided to not use a pass-through query and just call the SP from SQL using VBA:
'Stored procedure + parameters called from Form
strSQL = "Exec sqlsp_searchalltables " & Me.txtTables & _
", " & "'%" & Me.txtSearchTerm & "%'"Darlyne
Hi,
if you use "Execute" in a SQL string you can't use DAO and you must use ADO, that means: It is also a "pass-through" query as you are working with T-SQL and not with Access SQL...;-)
So there would be no difference if you used a "real" pass-through query or ADO, it's both T-SQL. PT Queries are read-only, with ADO you can also write to the result if needed.
A "UNION ALL" query means that you must have the exact number of columns in both (all) SELECTs which are part of the query. For example:
They also should have the same datatype in the corresponding columns (here: a and x, b and y, c and z) or you must cast them to the same datatype.
Cheers,
Christian
if you use "Execute" in a SQL string you can't use DAO and you must use ADO, that means: It is also a "pass-through" query as you are working with T-SQL and not with Access SQL...;-)
So there would be no difference if you used a "real" pass-through query or ADO, it's both T-SQL. PT Queries are read-only, with ADO you can also write to the result if needed.
A "UNION ALL" query means that you must have the exact number of columns in both (all) SELECTs which are part of the query. For example:
SELECT a,b,c FROM MyTable WHERE ....
UNION ALL
SELECT x,y,z FROM MyOtherTable WHERE....They also should have the same datatype in the corresponding columns (here: a and x, b and y, c and z) or you must cast them to the same datatype.
Cheers,
Christian
ASKER
Thanks for the additional information on pass-through queries, I didn't know the correct terminology. I am using ADO, but I may have a problem using the UNION ALL because although my column count can be equal, I not sure I can have the same datatypes. I'll check.
Hi,
the datatype can be cast to the wanted one, any datatype can be cast as a string for example.
If all other methods fail you could also add an additional parameter to your sp which you can use to only output the wanted return table. In this case you would need to call the same sp as often as needed with a different parameter so that the code in the sp remains in one place but the result set can be switched using this additional parameter.
Cheers,
Christian
the datatype can be cast to the wanted one, any datatype can be cast as a string for example.
If all other methods fail you could also add an additional parameter to your sp which you can use to only output the wanted return table. In this case you would need to call the same sp as often as needed with a different parameter so that the code in the sp remains in one place but the result set can be switched using this additional parameter.
Cheers,
Christian