Detect idle time on access database

[LG]

Hi,

I have recently used the Microsoft that will detect idle time coding on
my Access database and it works fine as long as you do not add any data
or move from one form to another. As soon as you do that, when idling
code kicks, an error message from Microsoft "Microsoft has
encountered a problem and needs to close" comes up.
Do you have any idea how that can be fixed?
Thank you in advance.

Liviu

[salad]

Re: Detect idle time on access database

LG wrote:

Hi,
>
I have recently used the Microsoft that will detect idle time coding on
my Access database and it works fine as long as you do not add any data
or move from one form to another. As soon as you do that, when idling
code kicks, an error message from Microsoft "Microsoft has
encountered a problem and needs to close" comes up.
Do you have any idea how that can be fixed?
Thank you in advance.
>
Liviu
>

I'd remove the Microsoft that detects idle time.

Seriously, how is idle time calculated/initiated? What's the code for
idle time?

You might want to Decompile your code then recompile. On the desktop
icon to open the database enter
/Decompile
at the end of the command

After you decompile, compact the database and then compile all of the
code. Remember to recome the /Decompile after you do that.

[LG]

Re: Detect idle time on access database

Here is the idling code that i'm using...

http://support.microsoft.com/?id=128814

salad wrote:

LG wrote:
>

Hi,

I have recently used the Microsoft that will detect idle time coding on
my Access database and it works fine as long as you do not add any data
or move from one form to another. As soon as you do that, when idling
code kicks, an error message from Microsoft "Microsoft has
encountered a problem and needs to close" comes up.
Do you have any idea how that can be fixed?
Thank you in advance.

Liviu

I'd remove the Microsoft that detects idle time.
>
Seriously, how is idle time calculated/initiated? What's the code for
idle time?
>
You might want to Decompile your code then recompile. On the desktop
icon to open the database enter
/Decompile
at the end of the command
>
After you decompile, compact the database and then compile all of the
code. Remember to recome the /Decompile after you do that.

[salad]

Re: Detect idle time on access database

LG wrote:

Here is the idling code that i'm using...
>

http://support.microsoft.com/?id=128814

>
>
>
>
salad wrote:
>

>>LG wrote:
>>
>>

>>>Hi,
>>>
>>>I have recently used the Microsoft that will detect idle time coding on
>>>my Access database and it works fine as long as you do not add any data
>>>or move from one form to another. As soon as you do that, when idling
>>>code kicks, an error message from Microsoft "Microsoft has
>>>encountere d a problem and needs to close" comes up.
>>>Do you have any idea how that can be fixed?
>>>Thank you in advance.
>>>
>>>Liviu
>>>

>>
>>I'd remove the Microsoft that detects idle time.
>>
>>Seriously, how is idle time calculated/initiated? What's the code for
>>idle time?
>>
>>You might want to Decompile your code then recompile. On the desktop
>>icon to open the database enter
>> /Decompile
>>at the end of the command
>>
>>After you decompile, compact the database and then compile all of the
>>code. Remember to recome the /Decompile after you do that.

>
>

Comment out the
On Error Resume Next
and see if your get a error you can debug

BTW, did you decompile/recompile?

[LG]

Re: Detect idle time on access database

commenting out 'On Error Resume Next' did not solve the problem.
i'll keep trying things. thank you.





salad wrote:

LG wrote:

Here is the idling code that i'm using...

http://support.microsoft.com/?id=128814

salad wrote:

>LG wrote:
>
>
>>Hi,
>>
>>I have recently used the Microsoft that will detect idle time coding on
>>my Access database and it works fine as long as you do not add any data
>>or move from one form to another. As soon as you do that, when idling
>>code kicks, an error message from Microsoft "Microsoft has
>>encountered a problem and needs to close" comes up.
>>Do you have any idea how that can be fixed?
>>Thank you in advance.
>>
>>Liviu
>>
>
>I'd remove the Microsoft that detects idle time.
>
>Seriously, how is idle time calculated/initiated? What's the code for
>idle time?
>
>You might want to Decompile your code then recompile. On the desktop
>icon to open the database enter
> /Decompile
>at the end of the command
>
>After you decompile, compact the database and then compile all of the
>code. Remember to recome the /Decompile after you do that.

Comment out the
On Error Resume Next
and see if your get a error you can debug
>
BTW, did you decompile/recompile?

[salad]

Re: Detect idle time on access database

LG wrote:

commenting out 'On Error Resume Next' did not solve the problem.
i'll keep trying things. thank you.
>

As I also asked, "BTW, did you decompile/recompile?"

>
>
>
>
salad wrote:
>

>>LG wrote:
>>

>>>Here is the idling code that i'm using...
>>>
>>>http://support.microsoft.com/?id=128814
>>>
>>>
>>>
>>>
>>>salad wrote:
>>>
>>>
>>>>LG wrote:
>>>>
>>>>
>>>>
>>>>>Hi,
>>>>>
>>>>>I have recently used the Microsoft that will detect idle time coding on
>>>>>my Access database and it works fine as long as you do not add any data
>>>>>or move from one form to another. As soon as you do that, when idling
>>>>>code kicks, an error message from Microsoft "Microsoft has
>>>>>encountere d a problem and needs to close" comes up.
>>>>>Do you have any idea how that can be fixed?
>>>>>Thank you in advance.
>>>>>
>>>>>Liviu
>>>>>
>>>>
>>>>I'd remove the Microsoft that detects idle time.
>>>>
>>>>Seriously , how is idle time calculated/initiated? What's the code for
>>>>idle time?
>>>>
>>>>You might want to Decompile your code then recompile. On the desktop
>>>>icon to open the database enter
>>>> /Decompile
>>>>at the end of the command
>>>>
>>>>After you decompile, compact the database and then compile all of the
>>>>code. Remember to recome the /Decompile after you do that.
>>>
>>>

>>Comment out the
>> On Error Resume Next
>>and see if your get a error you can debug
>>
>>BTW, did you decompile/recompile?

>
>