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

URGENT : need help with endless loop with requery code

P: n/a
Hi all,

I'm searching fulltime for days now, and I don't find the solution, so I'm
thinking this is more a bug :(

If i use following code in form&subforms:

Me.Parent![PeopleBase].Requery

Then sometimes (after 5, 6 or 20 times) i get an endless loop with 100% cpu
utilization (in the status bar you can see the note 'Calculating' !)

Some people put this code into the OnCurrent event and other say that this
is the cause. I tested the code everywhere (onclick, on change, etc...) and
still the same err occurs. Did err handling to fetch this loop but nothing.
I'm 100% sure that this line of code is giving me the loop problems. (Some
people reported that there was no problem in access97 and that it all
started with version 2000!)

If i search the net for this then you will find some 1000 msg reporting this
problem. I run through the most of them to find some solution, but nothing
did help yet.

Please, someone smarter then me, please help me with this, I can see it
anymore!

Thnx world.

ps: For your info, I'm using Access2000 eng on a Win2k eng sp4 platform (all
patches installed)

Nov 12 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
Hi all again,

ITS A BUG!!!!

http://support.microsoft.com/default...b;en-us;288374

Does someone has got good resolution for this ?

Thnx in advance


"John F." <jo**@clearmymind.com> wrote in message
news:3f**********************@reader1.news.skynet. be...
Hi all,

I'm searching fulltime for days now, and I don't find the solution, so I'm
thinking this is more a bug :(

If i use following code in form&subforms:

Me.Parent![PeopleBase].Requery

Then sometimes (after 5, 6 or 20 times) i get an endless loop with 100% cpu utilization (in the status bar you can see the note 'Calculating' !)

Some people put this code into the OnCurrent event and other say that this
is the cause. I tested the code everywhere (onclick, on change, etc...) and still the same err occurs. Did err handling to fetch this loop but nothing. I'm 100% sure that this line of code is giving me the loop problems. (Some
people reported that there was no problem in access97 and that it all
started with version 2000!)

If i search the net for this then you will find some 1000 msg reporting this problem. I run through the most of them to find some solution, but nothing
did help yet.

Please, someone smarter then me, please help me with this, I can see it
anymore!

Thnx world.

ps: For your info, I'm using Access2000 eng on a Win2k eng sp4 platform (all patches installed)

Nov 12 '05 #2

P: n/a
The link you provided gave the (perhaps unhelpful) solution of firing this
code from a diferent event, when you tried using diferent events to fire the
code did you delete the line of code from the OnCurrent event (just
checking)?

If so, perhaps you coud use a global variable and the Timer function to
produce code that will not refresh if it is within a certain amount of time
from a previous refresh?

--
Michael Hopwood (Phobos)
"John F." <jo**@clearmymind.com> wrote in message
news:3f***********************@reader3.news.skynet .be...
Hi all again,

ITS A BUG!!!!

http://support.microsoft.com/default...b;en-us;288374

Does someone has got good resolution for this ?

Thnx in advance


"John F." <jo**@clearmymind.com> wrote in message
news:3f**********************@reader1.news.skynet. be...
Hi all,

I'm searching fulltime for days now, and I don't find the solution, so I'm thinking this is more a bug :(

If i use following code in form&subforms:

Me.Parent![PeopleBase].Requery

Then sometimes (after 5, 6 or 20 times) i get an endless loop with 100%

cpu
utilization (in the status bar you can see the note 'Calculating' !)

Some people put this code into the OnCurrent event and other say that this is the cause. I tested the code everywhere (onclick, on change, etc...)

and
still the same err occurs. Did err handling to fetch this loop but

nothing.
I'm 100% sure that this line of code is giving me the loop problems. (Some people reported that there was no problem in access97 and that it all
started with version 2000!)

If i search the net for this then you will find some 1000 msg reporting

this
problem. I run through the most of them to find some solution, but nothing did help yet.

Please, someone smarter then me, please help me with this, I can see it
anymore!

Thnx world.

ps: For your info, I'm using Access2000 eng on a Win2k eng sp4 platform

(all
patches installed)


Nov 12 '05 #3

P: n/a
Hi Michael,

I did delete the code in the OnCurrent event when i was trying it on other
places. I even place it in a button, to fire it at own will. The weird thing
is that it I found out that it only happens when there was a previous delete
function fired on the table that gives a warning like : "The record cannot
be deleted or changed because table 'xxxx' includes related records.". If
you do then a Requery on the subforms then its bingo :( 100% cpu loop.

I'm using Access 2000, but the art stated acc2002, so I think this is a big
bug for years now.

I'm trying now to use the OnCurrent to fire some code that will fetch the
current record Key id and change the subform DataSourceQuery and refresh the
subform. I don't know about this, but its a shot I can do. If I have some
code i will post it here.

I don't want to use the timer function because it has nothing to do with "an
event1 that triggers event2 that triggers back event1.", because I use
buttons I only click ones, just for testing. I know, everybody is talking
about this back trigger, but i'm 100% sure this is not true.

For me, the Requery function just sucks, and is no good. Just a function to
stay away from. If it only happens 2 times on 10 then you know what I mean.

Hoop someone got some replacement code for this.

Cya all.

Thnx Michael,

JF

"Michael Hopwood" <la******@spammers.co.uk> wrote in message
news:J6********************@brightview.com...
The link you provided gave the (perhaps unhelpful) solution of firing this
code from a diferent event, when you tried using diferent events to fire the code did you delete the line of code from the OnCurrent event (just
checking)?

If so, perhaps you coud use a global variable and the Timer function to
produce code that will not refresh if it is within a certain amount of time from a previous refresh?

--
Michael Hopwood (Phobos)
"John F." <jo**@clearmymind.com> wrote in message
news:3f***********************@reader3.news.skynet .be...
Hi all again,

ITS A BUG!!!!

http://support.microsoft.com/default...b;en-us;288374

Does someone has got good resolution for this ?

Thnx in advance


"John F." <jo**@clearmymind.com> wrote in message
news:3f**********************@reader1.news.skynet. be...
Hi all,

I'm searching fulltime for days now, and I don't find the solution, so I'm thinking this is more a bug :(

If i use following code in form&subforms:

Me.Parent![PeopleBase].Requery

Then sometimes (after 5, 6 or 20 times) i get an endless loop with 100%
cpu
utilization (in the status bar you can see the note 'Calculating' !)

Some people put this code into the OnCurrent event and other say that this is the cause. I tested the code everywhere (onclick, on change,
etc...)
and
still the same err occurs. Did err handling to fetch this loop but

nothing.
I'm 100% sure that this line of code is giving me the loop problems. (Some people reported that there was no problem in access97 and that it all
started with version 2000!)

If i search the net for this then you will find some 1000 msg
reporting this
problem. I run through the most of them to find some solution, but nothing did help yet.

Please, someone smarter then me, please help me with this, I can see

it anymore!

Thnx world.

ps: For your info, I'm using Access2000 eng on a Win2k eng sp4

platform (all
patches installed)



Nov 12 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.