D
Daniel
Hello,
I have been using the following in my databases to determine if a form was
open or not
Function fIsLoaded(ByVal strFormName As String) As Integer
'Source: http://www.mvps.org/access/forms/frm0002.htm
'This Function Finds out if a form is open
'Returns a 0 if form is not open or a -1 if Open
If SysCmd(acSysCmdGetObjectState, acForm, strFormName) <> 0 Then
If Forms(strFormName).CurrentView <> 0 Then
fIsLoaded = True
End If
End If
End Function
However, going through the help file with access 2003, I came across the
..IsLoaded property. Is one method better than the other for determining if a
form is open? Is the .IsLoaded property new to access 2003? Are there any
pros or cons to continuing to use the function?
Thank you for the clarifications,
Daniel
I have been using the following in my databases to determine if a form was
open or not
Function fIsLoaded(ByVal strFormName As String) As Integer
'Source: http://www.mvps.org/access/forms/frm0002.htm
'This Function Finds out if a form is open
'Returns a 0 if form is not open or a -1 if Open
If SysCmd(acSysCmdGetObjectState, acForm, strFormName) <> 0 Then
If Forms(strFormName).CurrentView <> 0 Then
fIsLoaded = True
End If
End If
End Function
However, going through the help file with access 2003, I came across the
..IsLoaded property. Is one method better than the other for determining if a
form is open? Is the .IsLoaded property new to access 2003? Are there any
pros or cons to continuing to use the function?
Thank you for the clarifications,
Daniel