LinkBack URL
About LinkBacks
Here is the code. It works on Window 7 Professional, 64-bit, Office 2016. It does not work on Windows 7 Professional, 32-bit, Office 2013. I get the active X error message
Please Login or Register to view this content.
Here is the code. It works on Window 7 Professional, 64-bit, Office 2016. It does not work on Windows 7 Professional, 32-bit, Office 2013. I get the active X error message
Please Login or Register to view this content.
One spreadsheet to rule them all. One spreadsheet to find them. One spreadsheet to bring them all and at corporate, bind them.
A picture is worth a thousand words, but a sample spreadsheet is more likely to be worked on.
The Scripting library isn't dependent on Office version and should work with either bitness of Windows. Are you sure it hasn't been blocked by policy on one of the machines? Can you set a reference to the Scripting runtime and early bind the code on the problem machine just to test?
Everyone who confuses correlation and causation ends up dead.
Try re-registering the dll required.
In an admin command prompt:
regsvr32 c:\windows\system32\scrrun.dll
Edit: may need to use the /u flag first to unregister it.
regsvr32 /u c:\windows\system32\scrrun.dll
Last edited by Arkadi; 03-11-2019 at 09:24 AM.
Please help by:
Marking threads as closed once your issue is resolved. How? The Thread Tools at the top
Any reputation (*) points appreciated. Not just by me, but by all those helping, so if you found someone's input useful, please take a second to click the * at the bottom left to let them know
There are 10 kinds of people in this world... those who understand binary, and those who don't.
Arkadi: I re-registered the component and it was successful. I even rebooted the machine to be sure. The problem still persists. At home, I have instructions on how to de-register and re-register a DLL. It solved a rather knotty problem on my home machine. I will try that.
Rory: It has been a while since I've played with early and late binding and even then I barely "scraped through." Could you give me a hand with this and show me what I would have to do with the code? Thanks.
Set a reference to the Microsoft scripting runtime, then amend the code to:
though, as noted before, you don't actually need to use it here.Please Login or Register to view this content.
Aha! I get a compile error on this line:
"User-defined type not defined."Please Login or Register to view this content.
And this is on the "good" system!
As rorya said, you need to go to Tools->References and check the box next to Microsoft Scripting Runtime if you want to try early binding.
@dflak
Is this the same station that you had issue with Task Scheduler?It does not work on Windows 7 Professional, 32-bit, Office 2013.
I'd consider repairing/reinstall of Windows 7 environment. It seems to have bunch of issues.
Also, check hard-drive. You mentioned that you found bunch of bad sectors.
"Progress isn't made by early risers. It's made by lazy men trying to find easier ways to do something."
― Robert A. Heinlein
Do you even needIt doesn't seem that fso or oFile are used at all?Please Login or Register to view this content.
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
Register To Reply
Bookmarks