Office 2003 Standard upgrade nukes Access 2000

[JT]

We have Access 2000 installed on a per user basis on
several hundred PCs, along with Office 2000 Standard
(which is installed on a per computer basis).

The problem: When we upgrade to Office 2003 Standard
(using group policy, on a per computer basis), it
uninstalls Access 2000.

We've had Microsoft working on this problem for a couple
of weeks, to no avail. They say the problem is based in
the "reference count" for shared DLLs related to Access
2000. Apparently Office 2003 does some clean up based on
these reference counts (e.g. if count = 0, delete the
file).

The question: Does anyone have a solution? We'd really
like our Office 2003 Standard upgrade to skip this clean
up. MS says the OPC files can't be configured to skip
this.

Any help is greatly appreciated. Oh yes, we aren't using
SMS or Zenworks.


JT

 

[Gyorgy Moldova [MCSE, MVP]]

Couldn't you just install Access again on the computers over Office 2003?

Thanks,
g

 

[Gyorgy Moldova [MCSE, MVP]]

Couldn't you just install Access again on the computers over Office 2003?

Thanks,
g

 

[Gyorgy Moldova [MCSE, MVP]]

Couldn't you just install Access again on the computers over Office 2003?

Thanks,
g

 

[Gyorgy Moldova [MCSE, MVP]]

Couldn't you just install Access again on the computers over Office 2003?

Thanks,
g

 

[Gyorgy Moldova [MCSE, MVP]]

Couldn't you just install Access again on the computers over Office 2003?

Thanks,
g

 

[Gyorgy Moldova [MCSE, MVP]]

Couldn't you just install Access again on the computers over Office 2003?

Thanks,
g

 

[Gyorgy Moldova [MCSE, MVP]]

Couldn't you just install Access again on the computers over Office 2003?

Thanks,
g

 

[Gyorgy Moldova [MCSE, MVP]]

Couldn't you just install Access again on the computers over Office 2003?

Thanks,
g

 

[Gyorgy Moldova [MCSE, MVP]]

Couldn't you just install Access again on the computers over Office 2003?

Thanks,
g

 

[Bob Buckland ?:-\)]

Hi J.T.,

Probably good in this case to continue to work
through the MS Product support case assignment.

Trying to mix and match Office elements,
('per user' installs aren't recommended unless GPO is being used) as
these generally end up with some sort of upgrade problem when the upgrade
installation is 'per machine'.

Rinstalling Access 2000 in a 'per machine' scenario
afterwards is likely going to be the one to go with
although that 'out of sequence' install may require
a repair reinstall/recache of Office 2003.


========
We have Access 2000 installed on a per user basis on
several hundred PCs, along with Office 2000 Standard
(which is installed on a per computer basis).

The problem: When we upgrade to Office 2003 Standard
(using group policy, on a per computer basis), it
uninstalls Access 2000.

We've had Microsoft working on this problem for a couple
of weeks, to no avail. They say the problem is based in
the "reference count" for shared DLLs related to Access
2000. Apparently Office 2003 does some clean up based on
these reference counts (e.g. if count = 0, delete the
file).

The question: Does anyone have a solution? We'd really
like our Office 2003 Standard upgrade to skip this clean
up. MS says the OPC files can't be configured to skip
this.

Any help is greatly appreciated. Oh yes, we aren't using
SMS or Zenworks.


JT>>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

Office 2003 Editions explained
http://www.microsoft.com/uk/office/editions.mspx

 

[Bob Buckland ?:-\)]

Hi J.T.,

Probably good in this case to continue to work
through the MS Product support case assignment.

Trying to mix and match Office elements,
('per user' installs aren't recommended unless GPO is being used) as
these generally end up with some sort of upgrade problem when the upgrade
installation is 'per machine'.

Rinstalling Access 2000 in a 'per machine' scenario
afterwards is likely going to be the one to go with
although that 'out of sequence' install may require
a repair reinstall/recache of Office 2003.


========
We have Access 2000 installed on a per user basis on
several hundred PCs, along with Office 2000 Standard
(which is installed on a per computer basis).

The problem: When we upgrade to Office 2003 Standard
(using group policy, on a per computer basis), it
uninstalls Access 2000.

We've had Microsoft working on this problem for a couple
of weeks, to no avail. They say the problem is based in
the "reference count" for shared DLLs related to Access
2000. Apparently Office 2003 does some clean up based on
these reference counts (e.g. if count = 0, delete the
file).

The question: Does anyone have a solution? We'd really
like our Office 2003 Standard upgrade to skip this clean
up. MS says the OPC files can't be configured to skip
this.

Any help is greatly appreciated. Oh yes, we aren't using
SMS or Zenworks.


JT>>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

Office 2003 Editions explained
http://www.microsoft.com/uk/office/editions.mspx

 

[Bob Buckland ?:-\)]

Hi J.T.,

Probably good in this case to continue to work
through the MS Product support case assignment.

Trying to mix and match Office elements,
('per user' installs aren't recommended unless GPO is being used) as
these generally end up with some sort of upgrade problem when the upgrade
installation is 'per machine'.

Rinstalling Access 2000 in a 'per machine' scenario
afterwards is likely going to be the one to go with
although that 'out of sequence' install may require
a repair reinstall/recache of Office 2003.


========
We have Access 2000 installed on a per user basis on
several hundred PCs, along with Office 2000 Standard
(which is installed on a per computer basis).

The problem: When we upgrade to Office 2003 Standard
(using group policy, on a per computer basis), it
uninstalls Access 2000.

We've had Microsoft working on this problem for a couple
of weeks, to no avail. They say the problem is based in
the "reference count" for shared DLLs related to Access
2000. Apparently Office 2003 does some clean up based on
these reference counts (e.g. if count = 0, delete the
file).

The question: Does anyone have a solution? We'd really
like our Office 2003 Standard upgrade to skip this clean
up. MS says the OPC files can't be configured to skip
this.

Any help is greatly appreciated. Oh yes, we aren't using
SMS or Zenworks.


JT>>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

Office 2003 Editions explained
http://www.microsoft.com/uk/office/editions.mspx

 

[Bob Buckland ?:-\)]

Hi J.T.,

Probably good in this case to continue to work
through the MS Product support case assignment.

Trying to mix and match Office elements,
('per user' installs aren't recommended unless GPO is being used) as
these generally end up with some sort of upgrade problem when the upgrade
installation is 'per machine'.

Rinstalling Access 2000 in a 'per machine' scenario
afterwards is likely going to be the one to go with
although that 'out of sequence' install may require
a repair reinstall/recache of Office 2003.


========
We have Access 2000 installed on a per user basis on
several hundred PCs, along with Office 2000 Standard
(which is installed on a per computer basis).

The problem: When we upgrade to Office 2003 Standard
(using group policy, on a per computer basis), it
uninstalls Access 2000.

We've had Microsoft working on this problem for a couple
of weeks, to no avail. They say the problem is based in
the "reference count" for shared DLLs related to Access
2000. Apparently Office 2003 does some clean up based on
these reference counts (e.g. if count = 0, delete the
file).

The question: Does anyone have a solution? We'd really
like our Office 2003 Standard upgrade to skip this clean
up. MS says the OPC files can't be configured to skip
this.

Any help is greatly appreciated. Oh yes, we aren't using
SMS or Zenworks.


JT>>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

Office 2003 Editions explained
http://www.microsoft.com/uk/office/editions.mspx

 

[Bob Buckland ?:-\)]

Hi J.T.,

Probably good in this case to continue to work
through the MS Product support case assignment.

Trying to mix and match Office elements,
('per user' installs aren't recommended unless GPO is being used) as
these generally end up with some sort of upgrade problem when the upgrade
installation is 'per machine'.

Rinstalling Access 2000 in a 'per machine' scenario
afterwards is likely going to be the one to go with
although that 'out of sequence' install may require
a repair reinstall/recache of Office 2003.


========
We have Access 2000 installed on a per user basis on
several hundred PCs, along with Office 2000 Standard
(which is installed on a per computer basis).

The problem: When we upgrade to Office 2003 Standard
(using group policy, on a per computer basis), it
uninstalls Access 2000.

We've had Microsoft working on this problem for a couple
of weeks, to no avail. They say the problem is based in
the "reference count" for shared DLLs related to Access
2000. Apparently Office 2003 does some clean up based on
these reference counts (e.g. if count = 0, delete the
file).

The question: Does anyone have a solution? We'd really
like our Office 2003 Standard upgrade to skip this clean
up. MS says the OPC files can't be configured to skip
this.

Any help is greatly appreciated. Oh yes, we aren't using
SMS or Zenworks.


JT>>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

Office 2003 Editions explained
http://www.microsoft.com/uk/office/editions.mspx

 

[Bob Buckland ?:-\)]

Hi J.T.,

Probably good in this case to continue to work
through the MS Product support case assignment.

Trying to mix and match Office elements,
('per user' installs aren't recommended unless GPO is being used) as
these generally end up with some sort of upgrade problem when the upgrade
installation is 'per machine'.

Rinstalling Access 2000 in a 'per machine' scenario
afterwards is likely going to be the one to go with
although that 'out of sequence' install may require
a repair reinstall/recache of Office 2003.


========
We have Access 2000 installed on a per user basis on
several hundred PCs, along with Office 2000 Standard
(which is installed on a per computer basis).

The problem: When we upgrade to Office 2003 Standard
(using group policy, on a per computer basis), it
uninstalls Access 2000.

We've had Microsoft working on this problem for a couple
of weeks, to no avail. They say the problem is based in
the "reference count" for shared DLLs related to Access
2000. Apparently Office 2003 does some clean up based on
these reference counts (e.g. if count = 0, delete the
file).

The question: Does anyone have a solution? We'd really
like our Office 2003 Standard upgrade to skip this clean
up. MS says the OPC files can't be configured to skip
this.

Any help is greatly appreciated. Oh yes, we aren't using
SMS or Zenworks.


JT>>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

Office 2003 Editions explained
http://www.microsoft.com/uk/office/editions.mspx

 

[Bob Buckland ?:-\)]

Hi J.T.,

Probably good in this case to continue to work
through the MS Product support case assignment.

Trying to mix and match Office elements,
('per user' installs aren't recommended unless GPO is being used) as
these generally end up with some sort of upgrade problem when the upgrade
installation is 'per machine'.

Rinstalling Access 2000 in a 'per machine' scenario
afterwards is likely going to be the one to go with
although that 'out of sequence' install may require
a repair reinstall/recache of Office 2003.


========
We have Access 2000 installed on a per user basis on
several hundred PCs, along with Office 2000 Standard
(which is installed on a per computer basis).

The problem: When we upgrade to Office 2003 Standard
(using group policy, on a per computer basis), it
uninstalls Access 2000.

We've had Microsoft working on this problem for a couple
of weeks, to no avail. They say the problem is based in
the "reference count" for shared DLLs related to Access
2000. Apparently Office 2003 does some clean up based on
these reference counts (e.g. if count = 0, delete the
file).

The question: Does anyone have a solution? We'd really
like our Office 2003 Standard upgrade to skip this clean
up. MS says the OPC files can't be configured to skip
this.

Any help is greatly appreciated. Oh yes, we aren't using
SMS or Zenworks.


JT>>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

Office 2003 Editions explained
http://www.microsoft.com/uk/office/editions.mspx

 

[Bob Buckland ?:-\)]

Hi J.T.,

Probably good in this case to continue to work
through the MS Product support case assignment.

Trying to mix and match Office elements,
('per user' installs aren't recommended unless GPO is being used) as
these generally end up with some sort of upgrade problem when the upgrade
installation is 'per machine'.

Rinstalling Access 2000 in a 'per machine' scenario
afterwards is likely going to be the one to go with
although that 'out of sequence' install may require
a repair reinstall/recache of Office 2003.


========
We have Access 2000 installed on a per user basis on
several hundred PCs, along with Office 2000 Standard
(which is installed on a per computer basis).

The problem: When we upgrade to Office 2003 Standard
(using group policy, on a per computer basis), it
uninstalls Access 2000.

We've had Microsoft working on this problem for a couple
of weeks, to no avail. They say the problem is based in
the "reference count" for shared DLLs related to Access
2000. Apparently Office 2003 does some clean up based on
these reference counts (e.g. if count = 0, delete the
file).

The question: Does anyone have a solution? We'd really
like our Office 2003 Standard upgrade to skip this clean
up. MS says the OPC files can't be configured to skip
this.

Any help is greatly appreciated. Oh yes, we aren't using
SMS or Zenworks.


JT>>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

Office 2003 Editions explained
http://www.microsoft.com/uk/office/editions.mspx

 

[Bob Buckland ?:-\)]

Hi J.T.,

Probably good in this case to continue to work
through the MS Product support case assignment.

Trying to mix and match Office elements,
('per user' installs aren't recommended unless GPO is being used) as
these generally end up with some sort of upgrade problem when the upgrade
installation is 'per machine'.

Rinstalling Access 2000 in a 'per machine' scenario
afterwards is likely going to be the one to go with
although that 'out of sequence' install may require
a repair reinstall/recache of Office 2003.


========
We have Access 2000 installed on a per user basis on
several hundred PCs, along with Office 2000 Standard
(which is installed on a per computer basis).

The problem: When we upgrade to Office 2003 Standard
(using group policy, on a per computer basis), it
uninstalls Access 2000.

We've had Microsoft working on this problem for a couple
of weeks, to no avail. They say the problem is based in
the "reference count" for shared DLLs related to Access
2000. Apparently Office 2003 does some clean up based on
these reference counts (e.g. if count = 0, delete the
file).

The question: Does anyone have a solution? We'd really
like our Office 2003 Standard upgrade to skip this clean
up. MS says the OPC files can't be configured to skip
this.

Any help is greatly appreciated. Oh yes, we aren't using
SMS or Zenworks.


JT>>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

Office 2003 Editions explained
http://www.microsoft.com/uk/office/editions.mspx