gpupdate

[Keith Wilby]

Win XP Pro, A2k3 SP1.

Does anyone here work on a corporate client-server network where the IT
provider regularly runs "gpupdate" (group policy update)?

If so, have you found a way of mitigating for the "refresh" behaviour it
causes Access to exhibit? For example, when the policy update is run on a
user's PC, any dirty record in a subform will be saved without user
intervention. Is this something I'm stuck with?

Thanks.

Keith.

[Tom van Stiphout]

On Thu, 1 Mar 2007 12:59:00 -0000, "Keith Wilby" <he**@there.com>
wrote:

Explain further. I know a bit about GP, but AFAIK it does not
influence Access in this specific fashion. It's more about applying
security. It does not know about Access specifically, let alone about
dirty subforms.

-Tom.

>Win XP Pro, A2k3 SP1.

Does anyone here work on a corporate client-server network where the IT
provider regularly runs "gpupdate" (group policy update)?

If so, have you found a way of mitigating for the "refresh" behaviour it
causes Access to exhibit? For example, when the policy update is run on a
user's PC, any dirty record in a subform will be saved without user
intervention. Is this something I'm stuck with?

Thanks.

Keith.

[Keith Wilby]

"Tom van Stiphout" <no*************@cox.netwrote in message
news:t2********************************@4ax.com...

On Thu, 1 Mar 2007 12:59:00 -0000, "Keith Wilby" <he**@there.com>
wrote:

Explain further. I know a bit about GP, but AFAIK it does not
influence Access in this specific fashion. It's more about applying
security. It does not know about Access specifically, let alone about
dirty subforms.

Hi Tom, thanks for your reply.

When it runs on our PCs the screen flashes a few times and the Access window
appears to get refreshed - a dirty record in a subform will be saved but a
dirty record on a main form will not. More than that I can't explain, I
just wondered if it was one of "those" issues that was generally known about
but I hadn't encountered until now. I know that it's doing it because you
can force an update using the "/force" switch.

Regards,
Keith.

[Tom van Stiphout]

On Fri, 2 Mar 2007 08:27:31 -0000, "Keith Wilby" <he**@there.com>
wrote:

All I can think of is that GP might send a Windows Message to all
applications (typically this would be to all overlapped windows) to
refresh themselves, similar to WM_WININICHANGE. It would take some
doing to intercept them and see how best to respond to them. You may
just have to live with this.

-Tom.

>"Tom van Stiphout" <no*************@cox.netwrote in message
news:t2********************************@4ax.com.. .

>On Thu, 1 Mar 2007 12:59:00 -0000, "Keith Wilby" <he**@there.com>
wrote:

Explain further. I know a bit about GP, but AFAIK it does not
influence Access in this specific fashion. It's more about applying
security. It does not know about Access specifically, let alone about
dirty subforms.

Hi Tom, thanks for your reply.

When it runs on our PCs the screen flashes a few times and the Access window
appears to get refreshed - a dirty record in a subform will be saved but a
dirty record on a main form will not. More than that I can't explain, I
just wondered if it was one of "those" issues that was generally known about
but I hadn't encountered until now. I know that it's doing it because you
can force an update using the "/force" switch.

Regards,
Keith.

[Keith Wilby]

"Tom van Stiphout" <no*************@cox.netwrote in message
news:75********************************@4ax.com...

On Fri, 2 Mar 2007 08:27:31 -0000, "Keith Wilby" <he**@there.com>
wrote:

You may
just have to live with this.

As I feared. Thanks Tom.

Keith.