In the Database window, choose the Modules tab, and click New.
In the new module, create a function by typing:
Function WhateverYouWantToCallIt()
Access adds
End Function
Between the 2 lines, enter:
DoCmd.OpenForm "Form1"
Include the quotes. Replace Form1 with the name of your form.
To call the function from the macro, use the RunCode action. That's the
basics.
Here's a more comprehensive example.
Save the code below into your module.
In your macro, choose the StopMacro action, and put this beside it in the
Condition column (View menu if you don't see a Condition column):
Not FormOpened("Form1")
This will cause the macro to stop if the form did not open; otherwise it
continues to the next line.
For more information about error handling, see:
Error Handling in VBA
at:
http://allenbrowne.com/ser-23a.html
----------code starts-----------
Function FormOpened(strForm As String) As Boolean
On Error GoTo Err_Handler
'Argument: Name of the form to open
'Return: True if the form opened.
DoCmd.OpenForm strForm
FormOpened = True
Exit_Handler:
Exit Function
Err_Handler:
If Err.Number <> 2501 Then
MsgBox "Error " & Err.Number & " - " & Err.Description
End If
Resume Exit_Handler
End Function
----------code ends-----------
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users -
http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"John Baker" <Baker.JH@Verizon.net> wrote in message
news:ntnn90pmuvdq6c1hb5sktlsk7bndbjka6e@4ax.com...[color=blue]
> Thanks.
>
> Unfortunately my VBA sills are very very limited.
>
> How would I open a form (based on a query), check for an error and then[/color]
close the form if[color=blue]
> there was an error,or return to the main macro?
>
> If you could give me a simple outline of the commands required to do this[/color]
it would be a[color=blue]
> great help.
>
> Thanks
>
> John baker
>
> "Allen Browne" <AllenBrowne@SeeSig.Invalid> wrote:
>[color=green]
> >Macros have no error handling.
> >
> >As you found, they are only useful for a *very* limited range of things.
> >
> >Looks like you have outgrown them, and it's time to dip your feet into[/color][/color]
VBA[color=blue][color=green]
> >where error handling is part of every procedure you write.[/color]
>[/color]
