pass parameter to FE

From: smk2 (anonymous_at_discussions.microsoft.com)
Date: 03/26/04 

Date: Fri, 26 Mar 2004 04:36:07 -0800

I have SQL 2k BE with Access 2002 FE and need to pass an output value from a stored procedure back to Access.
Here is my current syntax:

Public Function InsertPhoneRecored () As Long
    Set cmdNew = New ADODB.Command
    With cmdNew
        .ActiveConnection = CurrentProject.Connection
        .CommandText = "procPhoneInsert"
        .CommandType = adCmdStoredProc
        .Execute
    End With
    
    InsertPhoneRecord = NewPhoneID
        
End Function

Where "NewPhoneID" is the parameter being passed from the stored procedure. How do I capture and use that value?
Thanks so much!
SMK

Relevant Pages

  • Re: Views vs Stored Procedures, whats the difference?
    ... I hope you are not suggesting you embed SQL queries into the application? ... A stored procedure logic will be exactly as fast as the algorithm you ... I understant that SQL Server supports hints. ... implementations (nestedloop, merge, hash, ..) on decent sized tables, then ...
    (comp.databases.ms-sqlserver)
  • Re: Stored Procedures - Patterns and Practices
    ... >published the reasoning behind its opinions. ... I disagree that the debate in SQL Server related discussion forums ... If the natural key is long or spans too many ... I want to call a stored procedure that adds a customer ...
    (microsoft.public.sqlserver.programming)
  • Re: Problem using SP as record source with Access2002 & SQL Server 7
    ... I've installed a brand new copy of SQL Server 2000 with the original ... I've created the folowing stored procedure for the resync ... Resync Command: ALL_CUSTOMERS_RESYNC? ... I need to upgrade to a newer version of Microsoft SQL ...
    (microsoft.public.access.adp.sqlserver)
  • Re: using Command to set Parameters and Recordset to retrive the Query
    ... doesn't the rsData will be interpretate as an input parameter in the SP? ... >> Query and retrive the Recordset so I can use the Paging property ... > Even if this technique of using the parameters in the ORDER BY does work for> you, I suspect that this will defeat your objective of preventing sql> injection. ... See below for a more efficient solution> using a stored procedure. ...
    (microsoft.public.inetserver.asp.general)
  • Re: slowing/halting stored procedure from ado.net
    ... but at the time when calling from the application ... calling the same stored procedure from SQL Management ... Studio goes without any slowdown, ... There was/is no big job running on the sql server, ...
    (microsoft.public.dotnet.framework.adonet)