pootle_flump
asked on
Access Runtime Installation has Unwelcome Effects
Hi
We are in discussions with a third party supplier due to problems caused by installation of their product. This product involves a local installation of Access 2000 Runtime despite the machines already having XP or 2003 installations. This causes all sorts of problems. We can get round some (e.g. the penchant for Access to open any database using the last used version of Access by using shortcut switches) however too many other things are screwed up for the situation to be considered acceptable. For example, the below code:
[Code]
Private Sub Command0_Click()
On Error GoTo Err_Command0_Click
Dim oAcc As Access.Application
Set oAcc = New Access.Application
oAcc.Visible = True
oAcc.OpenCurrentDatabase "C:\Test.mdb"
Set oAcc = Nothing
Exit_Command0_Click:
Exit Sub
Err_Command0_Click:
MsgBox Err.Description
Resume Exit_Command0_Click
End Sub
[/COde]
results in the below message:
>>
Please Wait while Windows configures Microsoft Access 200 SR-1 Runtime
Gathering required information
>>
as well as a progress meter.
Allowing it to run it's course results in:
>>
Error 1321. The installer has insufficient privileges to modify this file: C:\Program Files\Microsoft Office\ART\System\FM20.DLL
>>
And cancelling leads to:
>>
ActiveX component can’t create object
>>
The response from the vendor is predictable - "no one else has a problem". I'd like to go to them with a concrete "x is causing y and resulting in z" so we have some leverage to insist that they include a check for existing access components\ include the option NOT to install the runtime with future installations. Overall they are pretty responsive but I would like to be be a little less vague than "stuff stops working". Does any one have any ideas or experience of this? I know from the web that I am not unique in experiencing problems attributable to the runtime installation but I can't find specific mention of, for example, this problem.
Cheers Guys & thanks in advance
We are in discussions with a third party supplier due to problems caused by installation of their product. This product involves a local installation of Access 2000 Runtime despite the machines already having XP or 2003 installations. This causes all sorts of problems. We can get round some (e.g. the penchant for Access to open any database using the last used version of Access by using shortcut switches) however too many other things are screwed up for the situation to be considered acceptable. For example, the below code:
[Code]
Private Sub Command0_Click()
On Error GoTo Err_Command0_Click
Dim oAcc As Access.Application
Set oAcc = New Access.Application
oAcc.Visible = True
oAcc.OpenCurrentDatabase "C:\Test.mdb"
Set oAcc = Nothing
Exit_Command0_Click:
Exit Sub
Err_Command0_Click:
MsgBox Err.Description
Resume Exit_Command0_Click
End Sub
[/COde]
results in the below message:
>>
Please Wait while Windows configures Microsoft Access 200 SR-1 Runtime
Gathering required information
>>
as well as a progress meter.
Allowing it to run it's course results in:
>>
Error 1321. The installer has insufficient privileges to modify this file: C:\Program Files\Microsoft Office\ART\System\FM20.DLL
>>
And cancelling leads to:
>>
ActiveX component can’t create object
>>
The response from the vendor is predictable - "no one else has a problem". I'd like to go to them with a concrete "x is causing y and resulting in z" so we have some leverage to insist that they include a check for existing access components\ include the option NOT to install the runtime with future installations. Overall they are pretty responsive but I would like to be be a little less vague than "stuff stops working". Does any one have any ideas or experience of this? I know from the web that I am not unique in experiencing problems attributable to the runtime installation but I can't find specific mention of, for example, this problem.
Cheers Guys & thanks in advance
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks Sid - any idea where the Access 2000 Runtime default installation folder is?
ASKER
Anyone got any further ideas that can help me convince the supplier we need some changes making?