[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 372
  • Last Modified:

Erroneous results using date parameter in an Access function passed to a SQL stored procedure

I am receiving strange results when trying to pass a date value as a function parameter to a SQL stored procedure.
The following code is what I am using.  NOTE: I have tried various solutions such as; a date and/or a string type for the function parameter, also, a hard-coded value.

Here is the code:

Option Explicit

   
     'Function ParamSPT2(MyParam As String)
     Function ParamSPT2(MyParam As String)

     'MyParam = Format(MyParam, "yyyy-mm-dd hh:nn:ss")
     On Error GoTo ODBCErrHandler

        Dim MyDb As Database, MyQry As QueryDef, MyRS As Recordset
         Set MyDb = CurrentDb()
         Set MyQry = MyDb.CreateQueryDef("")

         ' Type a connect string using the appropriate values for your
         ' server.
         MyQry.connect = "ODBC;DSN=EPM_DEV;Description=EPM_Development;UID=user1;Trusted_Connection=Yes;DATABASE=PSEOC IBIXImport"

'MyParam = 2011 - 1 - 1
        MyParam = Format(MyParam, "yyyy-mm-dd hh:nn:ss")
         
         Debug.Print MyParam
         
         ' Set the SQL property and concatenate the variables.
         'MyQry.SQL = "sp_server_info " & MyParam
         MyQry.SQL = "Get_IBIX_Success_Totals_By_Date" & MyParam
         
         MyQry.ReturnsRecords = True
         Set MyRS = MyQry.OpenRecordset()
         MyRS.MoveFirst

         Debug.Print MyRS!attribute_id, MyRS!attribute_name, MyRS!attribute_value

         MyQry.Close
         MyRS.Close
         MyDb.Close
         
Exit_function:
   Exit Function
         
ODBCErrHandler:
   Dim errX As DAO.Error

   If Errors.Count > 1 Then
      For Each errX In DAO.Errors
         Debug.Print "ODBC Error"
         Debug.Print errX.Number
         Debug.Print errX.Description
      Next errX
   Else
      Debug.Print "VBA Error"
      Debug.Print Err.Number
      Debug.Print Err.Description
   End If
   Resume Exit_function
     
  End Function
0
psueoc
Asked:
psueoc
  • 5
  • 5
2 Solutions
 
derekkrommCommented:
MyQry.SQL = "Get_IBIX_Success_Totals_By_Date" & MyParam

there's no space between the proc name and the date - this may be the source of the issue

also, you probably need to wrap the parameter in quotes, like this:

MyQry.SQL = "Get_IBIX_Success_Totals_By_Date '" & MyParam & "'"

Open in new window

0
 
psueocAuthor Commented:
That helped but not out of the woods yet here are the results:
Why is it converting it to 1905-07-01 00:00:00?

?ParamSPT2(2011-01-01)
1905-07-01 00:00:00
VBA Error
 3265
Item not found in this collection.
0
 
derekkrommCommented:
I'm not sure - is that from the debug.print?

Try removing the format(). SQL should be able to handle that date format just fine without any additional processing.
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
psueocAuthor Commented:
Yes the 1901... was from debug.print.
I have removed formatting, here are the results.  The item not found probably means no records? Because it doesn't have the month and day portion needed for the query to run results?

2009
VBA Error
 3265
Item not found in this collection.
0
 
derekkrommCommented:
Did you put quotes around the whole thing? Copy/paste the line of code from my post above. You need to put single quotes around the parameter. Right now its seeing 2011-1-1 and interpreting it as an expression: hence 2009 being sent as a parameter instead of "2011-1-1"
0
 
psueocAuthor Commented:
I'm not sure about that because I copied your recommendation form above and it returned 2009.

MyQry.SQL = "Get_IBIX_Success_Totals_By_Date '" & MyParam & "'"
0
 
derekkrommCommented:
can you debug.print the myparam?
also debug.print this: "Get_IBIX_Success_Totals_By_Date '" & MyParam & "'"
0
 
psueocAuthor Commented:
Additional information:
 I have tried entering the parameter as follows at the Immediate window but without successful results:

?ParamSPT2(2011-01-01)

?ParamSPT2(2011/01/01)

?ParamSPT2(20110101)
0
 
derekkrommCommented:
how about this:

?ParamSPT2("2011-01-01")

0
 
psueocAuthor Commented:
Thank you very much. You have solved this problem.  I have follow-up which I will post immediately for additional points.
0

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

  • 5
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now