PRA: Form Design Changes Lost When 2nd Form's Timer Event Runs

Article ID: Q130334
Creation Date: 17-MAY-1995
Revision Date: 19-SEP-1996

The information in this article applies to:

Microsoft Access versions 2.0, 7.0

SYMPTOMS

Moderate: Requires basic macro, coding, and interoperability skills.

When you try to make design changes to a form (Form1) while you have a second form (Form2) open in Form view, you lose the design changes in Form1 when the OnTimer property event procedure for Form2 runs.

RESOLUTION

To work around this problem, do not make design changes to a form if you have a second form open in Form view and the second form has an event procedure set for its OnTimer property.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Access version 2.0 and Microsoft Access for Windows 95 version 7.0. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

Steps to Reproduce Problem

Open the sample database Northwind.mdb (or NWIND.MDB in version 2.0).

Open the Categories form in Design view.

Set the Categories form's OnTimer property to the following event procedure:
```
      Me.Timerinterval=4000
```
Set the Categories form's TimerInterval property to the following value:
```
      2000
```
View the Categories form in Form view and leave it open.
Open the Employees form in Design view.
Change the Extension label's Caption property setting to Phone#.
Note that after a few seconds, the Caption property changes from Phone# back to Extension when the Timer event is triggered on the Categories form.

REFERENCES

For more information about the Timer event, search for "Timer," and then "Timer Event" using the Microsoft Access Help menu.

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.