I have an Access mdb front end, which is linked to sql server tables via ODBC. I'd like to leverage sql server stored procedures to improve the performance, but I must maintain the front end as an mdb file (not adp).
Here is a specific scenario:
Form (frmAdoptionList) contains a listbox (lstAdoption) that currently uses a local query as it's record source (qlstAdoption). This query refers to two fields on the frmAdoptionList form to filter the listbox. For example:
SELECT dbo_sa_adoption.*
FROM dbo_sa_adoption
WHERE (((dbo_sa_adoption.locatio
I'm also using an AfterUpdate event procedure to requery listbox when user changes either of the two form field values, e.g.:
Private Sub cboLocation_AfterUpdate()
Me.lstAdoption.Requery
End Sub
I'd like to change row source of the listbox to instead use a store procedure and pass the two form field values so that I'm not pulling the entire record set across. To prepare for this, I've created a simple stored procedure named "sp_sa_lstAdoption" using this:
CREATE PROCEDURE [dbo].[sp_sa_lstAdoption]
@location varchar(50),
@adopted int
AS
SELECT dbo.sa_adoption.*
FROM dbo.sa_adoption
WHERE location = @location and adopted = @adopted
Using this specific example, can someone show me how to set the row source of the listbox to use the stored procedure that uses the two form parameters? I'm assuming I need to do something on the "OnOpen" event of the form containing the listbox, but I'm not sure exactly how to do it. I'm not used to setting connection strings in code, so specific guidance on what the resulting code should look like for the OnOpen event would be extremely helpful. If I can understand how to accomplish this once, I think I'll be able to figure out how to do it in other scenarios. Any help is much appreciated.
Regards,
Christopher
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
remember that all this is worthwhile when the back end table is large and the returning data is quite small, otherwise doing it locally in access will be as fast (or as slow...)
and also, note that you can call this sub (and use the query afterwards) for anything that runs on sqlserver, be it scalar, table (recordset) or nonquery (things that will run on the server internally) functions, storeprocs etc....
Thank you for your quick reply. I think I'm getting the concept, but still having problems making it work.
When the afterUpdate event is triggered, I'm receiving an error regarding the strSQL. It looks to me as the the correct stored procedure is being executed, but I'm not quite sure how to troubleshoot the problem. Here is a screencast showing what I've done and the resulting error:
http://www.screencast.com/
I know this is probably a very basic bonehead problem. Any help is much appreciated.
Thanks again,
Christopher
Thanks -- I actually tried it both ways and receive the same error, even without the quote (see attached).
Any other ideas what I could be doing wrong?
run time error
strSQL on debug
Business Accounts
Answer for Membership
by: ErezMorPosted on 2009-11-08 at 10:15:19ID: 25771251
there quite a few approaches to solve this, here's one:
create a passthrough query (it doesnt matter what it is, it's just to hold all connection information so you dont need to enter it every time)
now add a public sub in code:
Public Sub ChangePTquerySQL(strSQL As String)
Dim qdf As DAO.QueryDef
Set qdf = DBEngine(0)(0).QueryDefs("
q
Set qdf = Nothing
End Sub
now you can call this sub every time with the full sql passthrough syntax, and then set the result to your needs. so in your example you use the after update event of adoptValue and cboLocation in the Forms!frmAdoptionList:
if isNull(cboLocation)=False And IsNull(adoptValue)=False Then
ChangePTquerySQL "Exec dbo.sp_sa_lstAdoption '" & cboLocation & "'," & adoptValue & ";"
then, if lstAdoption rowsource is set to "qrySQLPassThrough" then
Me.lstAdoption.Requery
good luck