As Derek mentioned it wouldn't be practical in Access.
But you can can still create/use Stored Proc in Access....
Private Sub ProductsProcs()
Dim sSQL As String
' procProductsList - Retrieves entire table
sSQL = "CREATE PROC procProductsList AS SELECT * FROM Products;"
CreateStoredProc(sSQL)
' procProductsDeleteItem - Returns the details (one record) from the JobTitle table
sSQL = "CREATE PROC procProductsDeleteItem(inProductID LONG) " & _
"AS DELETE FROM Products WHERE ProductID = inProductID;"
CreateStoredProc(sSQL)
' procProductsAddItem - Add one record to the JobTitle table
sSQL = "CREATE PROC procProductsAddItem(inProductName VARCHAR(40), inSupplierID LONG, inCategoryID LONG) " & _
"AS INSERT INTO Products (ProductName, SupplierID, CategoryID) Values (inProductName, inSupplierID, inCategoryID);"
CreateStoredProc(sSQL)
' procProductsUpdateItem - Update one record on the JobTitle table
sSQL = "CREATE PROC procProductsUpdateItem(inProductID LONG, inProductName VARCHAR(40)) " & _
"AS UPDATE Products SET ProductName = inProductName WHERE ProductID = inProductID;"
CreateStoredProc(sSQL)
End Sub
Private Sub CreateStoredProc(ByVal sSQL As String)
Dim con As OleDbConnection
Dim cmd As OleDbCommand = New OleDbCommand()
Dim da As OleDbDataAdapter
Dim sConStr As String = "PROVIDER=Microsoft.Jet.OLEDB.4.0;Data Source=c:\Northwind.mdb"
con = New OleDbConnection(sConStr)
cmd.Connection = con
cmd.CommandText = sSQL
con.Open()
cmd.ExecuteNonQuery()
con.Close()
End Sub