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!
I thought the whole point of the CableCard was that it was supposed to work, and be a consumer friendly thing!! Now they're saying the CableCard won't necessarily work?? Or is it just that you'll have to get a new Cable Card?
The way I understand it is, the CableCard lets the device that uses it receive all the channels that come over your cable. The problem is, we're gonna start to see cable companies stop sending certain less-popular channels unless your cable box sends a signal to the cable company asking for the channel. CableCard currently does not have this ability to send these requests. This is the same reason CableCard does not currently work with pay-per-view.
Since I can't afford a new Tivo right now anyway, I think the TruWay stuff sounds pretty darn neat. I assume it means more HD channels too. Whee!
Any Excel VBA gurus around? I've written a bunch of macros that use this nifty functionality that lets me call an Attachmate Extra 3270 session from within the macro. Using the GetObject function, the Attachmate app opens, I automagically connect to a session and can send information back and forth between the two apps. It's really useful for copying and pasting data from my company's mainframe into a spreadsheet. It works great and has saved me a lot of work.
The problem is when I have other people run the same macro. For some people, it works fine; for others, the Attachmate application doesn't open and the macro ends without doing anything.
I can't for the life of me figure out why it works for some people and not others. We're all using Windows XP Pro and the same versions of Excel and Attachmate. Could admin privileges have something to do with it? I have them, but the other people might not.
Errrhg. It's not about whether you're an administrator. It worked fine on someone's machine here who's not.
How are you liking it Jesse?
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.
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....
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.
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....
