P
patti
I have a report that has lots of stuff going on behind it. It ran fine weekly
til today.
I have compacted & repaired. I have also recalled an old copy of the db,
relinked tables, and tried to run report again - still hanging. "Access not
responding".
From strSQL(abridged version)
SELECT....fnGetPO([ON Order PO Info].[m1 po],[ON Order PO Info].[m2 PO],...
____________________________
this is the module for the fnGetPO (abridged version)
Public Function fnGetPO(po1, po2, po3, po4) As String
Dim strPO As String
If Not IsNull(po1) Then
strPO = po1
Else
If Not IsNull(po2) Then
strPO = po2
Else
If Not IsNull(po3) Then
strPO = po3
Else
If Not IsNull(po4) Then
strPO = po4
Else
strPO = "None"
End If
End If
End If
End If
fnGetPO = strPO
End Function
___________________________________________
Thanks to Roger Carlson ( MS Access MVP) i stepped through my code with f8.
i just loop and loop and loop through the function.
I am really confused since it was working the past few months. Is it an
issue with the code? Perhaps this week's data itself? Is anything obviously
wrong here? Gut feelings are always welcome too!
Thanks for the help.
til today.
I have compacted & repaired. I have also recalled an old copy of the db,
relinked tables, and tried to run report again - still hanging. "Access not
responding".
From strSQL(abridged version)
SELECT....fnGetPO([ON Order PO Info].[m1 po],[ON Order PO Info].[m2 PO],...
____________________________
this is the module for the fnGetPO (abridged version)
Public Function fnGetPO(po1, po2, po3, po4) As String
Dim strPO As String
If Not IsNull(po1) Then
strPO = po1
Else
If Not IsNull(po2) Then
strPO = po2
Else
If Not IsNull(po3) Then
strPO = po3
Else
If Not IsNull(po4) Then
strPO = po4
Else
strPO = "None"
End If
End If
End If
End If
fnGetPO = strPO
End Function
___________________________________________
Thanks to Roger Carlson ( MS Access MVP) i stepped through my code with f8.
i just loop and loop and loop through the function.
I am really confused since it was working the past few months. Is it an
issue with the code? Perhaps this week's data itself? Is anything obviously
wrong here? Gut feelings are always welcome too!
Thanks for the help.