I'm going to have to get used to it. Really, once I get all the settings straightened out, I'm sure I won't even notice it -- especially given that we already have Office 2007 here at work.
Time for some thrilling heroics.
Jayne ,'The Train Job'
Buffistechnology 3: "Press Some Buttons, See What Happens."
Got a question about technology? Ask it here. Discussion of hardware, software, TiVos, multi-region DVDs, Windows, Macs, LINUX, hand-helds, iPods, anything tech related. Better than any helpdesk!
Jesse - Apr 17, 2008 5:12:17 am PDT #5762 of 25501
Sometimes I trip on how happy we could be.
tommyrot - Apr 17, 2008 5:21:23 am PDT #5763 of 25501
Sir, it's not an offence to let your cat eat your bacon. Okay? And we don't arrest cats, I'm very sorry.
Jon B., does everyone have the exact same installation of Office? Maybe some were installed with the scripting option (or whatever it's called during installation) selected, and some without? Anyway, if you haven't already, I'd start by verifying that macros work at all on the "bad" machines....
Jon B. - Apr 17, 2008 5:29:58 am PDT #5764 of 25501
A turkey in every toilet -- only in America!
Macros, in general, do work on all the machines. Actually, it turns out that one person whose machine I thought didn't run the Attachmate macro, DOES run the macro. This changes some of my earlier assumptions. It may be related to the version of Attachmate after all. I need to test on some more machines and will report back.
tommyrot - Apr 17, 2008 5:36:02 am PDT #5765 of 25501
Sir, it's not an offence to let your cat eat your bacon. Okay? And we don't arrest cats, I'm very sorry.
Jon, does the macro report any errors when it runs? Can you put in some error-trapping in the code that does the connection? Failing that (eta: if that doesn't give you the error), once your macro has instantiated the object, are there any properties you can read regarding its status?
eta²: or you could put a Stop in the code and step through to see where the problem is....
Jon B. - Apr 17, 2008 6:40:42 am PDT #5766 of 25501
A turkey in every toilet -- only in America!
Jon, does the macro report any errors when it runs?
Run-Time error '429'
ActiveX component can't create object.
It bombs on the CreateObject or GetObject functions.
It's almost definitely related to the version of Attachmate. I'm using Attachmate Extra! 6.5. The folks on whose machines it bombs are using Attachmate Extreme! 8.0.
I wish I was making up the names of those programs.
Tom Scola - Apr 17, 2008 8:39:28 am PDT #5767 of 25501
Remember that the frontier of the Rebellion is everywhere. And even the smallest act of insurrection pushes our lines forward.
More on CableCard and TiVo: [link]
omnis_audis - Apr 17, 2008 8:15:08 pm PDT #5768 of 25501
omnis, pursue. That's an order from a shy woman who can use M-16. - Shir
Mac vs PC shootout in Popular Mechanics: [link] First blush says Mac has unfair advantage, with a slightly faster processor (2.2 GHz vs 2.4 GHz) The interesting thing I saw was, they tested Vista on the Mac hardware. Generally speaking, Vista ran better on the Mac. And Mac OS-X ran better than Vista.
(not wanting to start a us vs them war here, just pointing out that it's interesting... even if I think the test situation was less than matched). My favorite quote tho is:
Our biggest surprise, however, was that PCs were not the relative bargains we expected them to be. The Asus M51sr costs the same as a MacBook, while the Gateway One actually costs $300 more than an iMac. That means for the price of the Gateway you could buy an iMac, boost its hard drive to match the Gateway’s, purchase a copy of Vista to boot—and still save $100.
§ ita § - Apr 17, 2008 11:12:12 pm PDT #5769 of 25501
Well not canonically, no, but this is transformative fiction.
I have a fresh Vista install. I made a set of recovery disks so that I could swap out the drive that came with the box for a smaller one. I then recovered onto the smaller drive and proceeded about reinstalling apps--but now I'm having problems with an .msi file--it tells me that "The system administrator has set policies to prevent this installation."
No I didn't! It's exactly the same security as the first time I had the system setup. I can't work out how to make it go away. I have only the one user, and I've been able to install many other programs--I don't know if it's balking because it's a yaddayadda.msi instead of setup.exe.
Does this set of a flag for anyone?
DCJensen - Apr 18, 2008 5:51:19 am PDT #5770 of 25501
All is well that ends in pizza.
sounds like a job for secpol.msc.
I've only used it a few times myself, but here's a MS page on the command: [link]
§ ita § - Apr 18, 2008 6:56:21 am PDT #5771 of 25501
Well not canonically, no, but this is transformative fiction.
I ended up rolling back to a restore point--which isn't flawless, and seems to have left me unable to uninstall some applications (I guess because the app files are gone because I uninstalled them before the restore), but I want the entries out of my installed programs view.