Network Group Policy causes form-datasheet requery

[Danny J. Lesandrini]

-- previously posted on newsgroup :: <microsoft.publ ic.access--

Has anyone else noticed this behavior?
Focus jumping from current cell to upper left in embedded datasheet.
If not, would you be willing to test your environment and report back?
I posted this question back in May because a client using our application
reported it. We could only reproduce it on our network if we modified the
configuration. Now, however, it's happening all over the place.

A link to the original post is shown here, but I'll rephrase the question below ...
http://groups.google.com/group/micro...66e949b9275b59
Problem:
--------------------------------------
Parent form with record source has an embedded subform that is linked
on Master/Child fields. Subform is a datasheed with multiple rows visible.
Without warning, the screen flashes and the focus jumps to the first row,
first column.
Steps to Reproduce:
--------------------------------------
1) Open any form with a datasheet subform linked on Master/Child fields
2) Place cursor in any cell, down a few rows and over a few columns
3) Open a command window and execute this: gpUpdate /force
(this forces update of the network group policy)
(answer no (N) to prompts to reboot and logoff)
4) Watch the cursor in your datasheet subform jump to top left cell.
This may not happen to you. We worked with Microsoft on this for weeks
and got no resolution. Suggestions were made of how we might redesign
our forms, but they didn't help.

Our client tracked it down to a network group policy setting for IE and
since their draconian approach to security forced the update every 5 mins,
their users were going nuts with the cursor jumping out of their boxes all
the time. Not to mention that it promotes data entry errors

I'd appreciate hearing back from anyone who can reproduce this. If we get
enough of us, maybe Microsoft will be forced to figure it out. The only solution
we could come up with was to change the group policy refresh from its default
of 90 minutes to 12 hours ... but that seems like a kludge.

Thanks
--

Danny J. Lesandrini
dl*********@hot mail.com
http://amazecreations.com/datafast

[David W. Fenton]

"Danny J. Lesandrini" <dl*********@ho tmail.comwrote in
news:I7******** *************** *******@comcast .com:

Our client tracked it down to a network group policy setting for
IE and since their draconian approach to security forced the
update every 5 mins, their users were going nuts with the cursor
jumping out of their boxes all the time. Not to mention that it
promotes data entry errors

Why in the world would a network administrator push security
policies down at any time other than domain logon?

That's complete idiocy on their part, and the source of the problem.
In other words, MS is not likely to ever fix such a problem, as it's
caused by a wrong implementation of policy propagation.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

[Lyle Fairfield]

Danny J. Lesandrini wrote:

-- previously posted on newsgroup :: <microsoft.publ ic.access--

Has anyone else noticed this behavior?
Focus jumping from current cell to upper left in embedded datasheet.
If not, would you be willing to test your environment and report back?
I posted this question back in May because a client using our application
reported it. We could only reproduce it on our network if we modified the
configuration. Now, however, it's happening all over the place.

A link to the original post is shown here, but I'll rephrase the question below ...
http://groups.google.com/group/micro...66e949b9275b59
Problem:
--------------------------------------
Parent form with record source has an embedded subform that is linked
on Master/Child fields. Subform is a datasheed with multiple rows visible.
Without warning, the screen flashes and the focus jumps to the first row,
first column.
Steps to Reproduce:
--------------------------------------
1) Open any form with a datasheet subform linked on Master/Child fields
2) Place cursor in any cell, down a few rows and over a few columns
3) Open a command window and execute this: gpUpdate /force
(this forces update of the network group policy)
(answer no (N) to prompts to reboot and logoff)
4) Watch the cursor in your datasheet subform jump to top left cell.
This may not happen to you. We worked with Microsoft on this for weeks
and got no resolution. Suggestions were made of how we might redesign
our forms, but they didn't help.

Our client tracked it down to a network group policy setting for IE and
since their draconian approach to security forced the update every 5 mins,
their users were going nuts with the cursor jumping out of their boxes all
the time. Not to mention that it promotes data entry errors

I'd appreciate hearing back from anyone who can reproduce this. If we get
enough of us, maybe Microsoft will be forced to figure it out. The only solution
we could come up with was to change the group policy refresh from its default
of 90 minutes to 12 hours ... but that seems like a kludge.

Thanks
--

Danny J. Lesandrini
dl*********@hot mail.com
http://amazecreations.com/datafast

Can we save the location of the active cell on its getting the focus?
Can we identify an event that occurs on requery (or on gpUpdate)?
Can we program that event to "activate" the cell at the saved location?

Sometimes with MS one must just say, "Do your worst, I'm gonna win
regardless."

[Danny J. Lesandrini]

Draconian, I agree, but the default out of the "Microsoft box" is 90 minutes.
I'd say that makes it their problem.

--
Danny J. Lesandrini
dl*********@hot mail.com
www.amazecreations.com/datafast/

"David W. Fenton" <XX*******@dfen ton.com.invalid wrote in message
news:Xn******** *************** ***********@127 .0.0.1...

"Danny J. Lesandrini" <dl*********@ho tmail.comwrote in
news:I7******** *************** *******@comcast .com:

>Our client tracked it down to a network group policy setting for
IE and since their draconian approach to security forced the
update every 5 mins, their users were going nuts with the cursor
jumping out of their boxes all the time. Not to mention that it
promotes data entry errors

Why in the world would a network administrator push security
policies down at any time other than domain logon?

That's complete idiocy on their part, and the source of the problem.
In other words, MS is not likely to ever fix such a problem, as it's
caused by a wrong implementation of policy propagation.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/