macro errors after 2003 upgrade!

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Stephanie (anonymous_at_discussions.microsoft.com)
Date: 02/09/04


Date: Mon, 9 Feb 2004 13:58:21 -0800

It is a bug. hope the following workaround from Microsoft
helps...

Microsoft told me there is a bug with the "Visible"
property of the form (which is how the Help file says to
create an OK button for your form). Instead, select the
imput form and open it in design view by clicking Design
icon on the toolbar. In its design View, right-click the
OK button and select Property menu to open its Properties
dialog. On the Event tab, select the [Event Procedure]
option for the On Click event. Using the VBA editor, make
the event procedure as follows:

Private Sub OK_Click()
     Me.Visible = False
End Sub

Hope that helps!

>-----Original Message-----
>I asked this question at xmas without response...hope
>somebody sees it and can help this time:
>
>I created a db in Access 2000. There are several reports
>which are each built upon several parameter queries. I
use
>a form to ask for the parameter which then supplies the
>parameter to all queries and prints the parameter in the
>report. On opening the report the macro opens the form
>asking for user input, the OK button on the form hides
the
>form, keeping it open, so the queries can access the
>parameter. Closing the report closes the form. This is
>straight from Access Help files and is something my users
>use daily. It has always worked beautifully.
>
>I upgraded to Access 2003 and now the macro errors at the
>SetValue action (Object: my input form, Property:
>[Visible] Value: No). Sometimes I get the message that I
>need to register my Active X control, but I am only using
>the standard command button on the form toolbox. I have
>seen a few other posts here describing a similar problem.
>Does anyone know about how to solve this? Please! is this
>a bug with 2003? I can't allow my company to install the
>upgrades we already obtained if the databases won't work
>after!
>
>Thanks for your help.
>
>.
>



Relevant Pages

  • RE: Combo box parameter report
    ... open, in which case it opens the form, passing the report's name to it as its ... the report is then opened from a button on the form. ... The code for the report's Open event procedure is: ... Private Sub Report_Open ...
    (microsoft.public.access.queries)
  • Re: Sort
    ... The code should be in the event procedure associated with the report's Open ... But it does not get implemented when the report ... >>>Hi Lloyd ... >>>> This opens the report with the records selected by the ...
    (microsoft.public.access.formscoding)
  • Re: Printing unbound text boxes with a chart
    ... What you are suggesting should be fine if the form is still open. ... If you wish to make the report independent of the form after it opens, ... > diable the event procedure, ...
    (microsoft.public.access.reports)
  • Re: Testing for empty Querys
    ... the Event Procedure of the On No Data event of your report look like the ... report that may be affecting evaluation of the On No Data event? ... I tested it and it still opens. ...
    (microsoft.public.access.formscoding)
  • Re: Printer Object wont persist
    ... I'm not sure I'd call this a bug. ... If you open the report in print preview, run the same line, and close, the setting is not saved ... Tips for Access users - http://allenbrowne.com/tips.html ... funtction checks the property, sets the printer, opens the report, and then ...
    (microsoft.public.access.reports)