Home |
Search |
Today's Posts |
#2
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
Oh buggrit buggrit buggrit. Found it.
I instantiate Excel using Set oExcel = CreateObject("Excel.application") So that I don't have to worry about the version of the target machines. For some reason this is instantiating Excel 2002 which DIDN'T have "Trust Access to Visual Basic Project" enabled. Now, since I have 2003 installed, how come OLE is running 2002? Rob "Rob Kings" wrote in message ... Hi I've got some VB code that uses OLE automation to do some stuff in Excel. I've started getting the error "programmatic access to visual basic project is not trusted" but I DO have the setting "Trust Access to Visual Basic Project" enabled. Interesting points to note: 1. This code has been working (certainly it was last week) 2. If I run my routine from inside Excel then its OK 3. Because of some other problems (A Microsoft security update breaking something) I had to go back to a restore point. When I then went to Microsoft update (to prevent the same download happening again) I got 148Mb of stuff which included lots of Office 2003 "fixes". Is it possible that they broke something else? Any ideas? |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
Trust Access to Visual Basic Project | Excel Programming | |||
Programmactic access to Visual Basic Project is not trusted | Excel Programming | |||
Programmatic Access to Visual Basic Project is not Trusted | Excel Programming | |||
'Programmatic access to Visual Basic project is not trusted.' message | Excel Programming | |||
Allow access to visual basic project | Excel Programming |