By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
446,201 Members | 922 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 446,201 IT Pros & Developers. It's quick & easy.

Detect idle time on access database

P: n/a
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

Sep 28 '06 #1
Share this Question
Share on Google+
5 Replies


P: n/a
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.

Sep 29 '06 #2

P: n/a
LG
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.
Sep 29 '06 #3

P: n/a
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?
Sep 29 '06 #4

P: n/a
LG
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?
Oct 2 '06 #5

P: n/a
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
>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?

Oct 2 '06 #6

This discussion thread is closed

Replies have been disabled for this discussion.