Hi all

I have a mdb application to develop when I get into design mode for a form
or a module is found that the code still running. and sometimes when I open
a form in design mode to make any changes the application runs the events on
that form , I don't know what makes this problem please advice.

thanks

Wael

SS wrote:
> Hi all
>
> I have a mdb application to develop when I get into design mode for a form
> or a module is found that the code still running. and sometimes when I open
> a form in design mode to make any changes the application runs the events on
> that form , I don't know what makes this problem please advice.
>
> thanks
>
> Wael

My guess is that you have an opening form, quite possibly utilizing a
timer, that is still left open when you open other forms in design view.

If that's the case, close this form first.

--
Roy-Vidar

"RoyVidar" <(E-Mail Removed)> wrote in message
news:46c40186$0$7443$(E-Mail Removed)...
> SS wrote:
>> Hi all
>>
>> I have a mdb application to develop when I get into design mode for a
>> form or a module is found that the code still running. and sometimes when
>> I open a form in design mode to make any changes the application runs the
>> events on that form , I don't know what makes this problem please advice.
>>
>> thanks
>>
>> Wael
>
> My guess is that you have an opening form, quite possibly utilizing a
> timer, that is still left open when you open other forms in design view.
>
> If that's the case, close this form first.
>
> --
> Roy-Vidar

hi Roy-Vidar

I had removed all timers from the forms and still have the same problem.

thanks

Wael

SS wrote:
> "RoyVidar" <(E-Mail Removed)> wrote in message
> news:46c40186$0$7443$(E-Mail Removed)...
>> SS wrote:
>>> Hi all
>>>
>>> I have a mdb application to develop when I get into design mode for a
>>> form or a module is found that the code still running. and sometimes when
>>> I open a form in design mode to make any changes the application runs the
>>> events on that form , I don't know what makes this problem please advice.
>>>
>>> thanks
>>>
>>> Wael
>> My guess is that you have an opening form, quite possibly utilizing a
>> timer, that is still left open when you open other forms in design view.
>>
>> If that's the case, close this form first.
>>
>> --
>> Roy-Vidar
>
> hi Roy-Vidar
>
> I had removed all timers from the forms and still have the same problem.
>
> thanks
>
> Wael

Then I don't know.

- hm - removed all tiemers from the forms - you're sure you've also
removed/commented any code invoking timers ;-)

If you still have other forms open, for instance opened with the
acDialog option, I think one might experience that the VBE
says code is still running. Hitting the reset button should "fix"
that, as far as I know, without causing any problems.

Corruption
One might perhaps suspect corruption. If corruption is the issue,
you could try one of the following methods on a *copy* of the db

- import all objects to a new database

- try /decompile
(see http://www.granite.ab.ca/access/decompile.htm for step by step
instructions - and - between step 2 and 3, again close all isntances
of Access, and compact the db in another instance of Access than the
one you /decompiled with)

- try the hidden methods SaveAsText/LoadFromText of the application
object. For an automated version, see for instance Arvin Meyers
http://www.datastrat.com/Code/DocDatabase.txt, which demonstrates
the SaveAsText method. For the other way around, loop the different
filetypes, and use LoadFromText with the same syntax


--
Roy-Vidar