L
LeighP
We have a client - remote with own IT (i.e. have never seen this setup
personally).
They're running Windows Server 2003 Standard Edition Terminal Services.
The server has Office 2003 Standard Edition installed on it.
We have an Access 2003 Runtime application recently installed on it.
This same runtime application has successfully installed on many hundreds of
PCs and indeed several TS servers perfectly well.
It's an Access 2003 Runtime wrapped in an Installshield expression package
(uses an MSI).
On this one instance - every attempt to launch the application file (an
Access mde) sees the whole install of the package fire up and attempt to run
again.
It has been fully removed - and then installed again clean. But the
behaviour persists.
Every launch of either the MDE file (or even the MSAcess.exe itself!) merely
relaunches the whole package installer.
This behaviour occurs for Admin as well as limited users.
Any thoughts would be most welcome indeed! :-S
Many thanks.
personally).
They're running Windows Server 2003 Standard Edition Terminal Services.
The server has Office 2003 Standard Edition installed on it.
We have an Access 2003 Runtime application recently installed on it.
This same runtime application has successfully installed on many hundreds of
PCs and indeed several TS servers perfectly well.
It's an Access 2003 Runtime wrapped in an Installshield expression package
(uses an MSI).
On this one instance - every attempt to launch the application file (an
Access mde) sees the whole install of the package fire up and attempt to run
again.
It has been fully removed - and then installed again clean. But the
behaviour persists.
Every launch of either the MDE file (or even the MSAcess.exe itself!) merely
relaunches the whole package installer.
This behaviour occurs for Admin as well as limited users.
Any thoughts would be most welcome indeed! :-S
Many thanks.