Framework X Library

[JandC]

Both Word and Excel show a message about unexpected error loading
Framework X Library, then usually "quit unexpectedly"
I have tried looking for locked files and duplicate Fonts and reloading the
programs, and other hints I have found... still the same. Driving me nuts.

 

[Ramón G Castañeda]

Both Word and Excel show a message about unexpected error loading
Framework X Library, then usually "quit unexpectedly"
I have tried looking for locked files and duplicate Fonts and reloading the
programs, and other hints I have found... still the same. Driving me nuts.

Could you provide a few more hints? Exact versions of the applications and
of your operating system, your machine, RAM, available hard disk space, what
have you tried so far, what routine maintenance you perform, etc.

 

[Guest]

Powerbook G4, 867MgHZ, 640MB Ram. System 10.3.4
Office - Word X for Mac, V 10.1.4,
Tried looking for duplicated fonts. Tried looking for locked files. Tried
reloading program. thank you.

 

[Jim Meador]

I'm having a similar problem but more specifically what seems to be
happening is that several files and applications in the Office folder are
looking like "Python Plugin Module" documents to MacOS10.3.4. I'm trying to
use a Visual Basic Macro I made in Office but it can't be opened. If I
reinstall Office, I can get Visual Basic to start up and can edit my macro,
but as soon as I apply the Office X 10.1.2 Update or above Visual Basic
stops being able to be opened. If I look at the various files that are
affected with Xray, such as Visual Basic for Applications, its creator code
is "VBE" which is unknown to Xray, and the Type code is "shlb" which appears
to be a Python Plugin Module ('shlb') to Xray. So I am guessing that this
may be the root of the problem even though it appears to be the same after a
clean reinstall of Office when everything works. I can go back to that, but
it seems to me to be a bit risky. I'm using a PowerbookG3 400MHz Firewire
(Pismo) with MacOSX10.3.4 and 768 megs. I recently had to install a new
harddrive and have just about got everything working again, except Microsoft
Office...

If anyone has an idea of how to fix this, I'd appreciate it a lot.
Thanks,
Jim

 

[Jim Meador]

After much experimentation, I am convinced that the two are not compatible.
I would love to hear from someone who thinks otherwise, however, before you
pounce on the reply button, the problem I have is with the shared libraries
in Office such as Visual Basic for Applications, Microsoft Component Plugin,
MS OLE Automation (Carbon), etc. etc. They are not apparently owned by
Office due to conflicts with type/creator codes, even though MacOSX was
supposed to have "progressed" past them (regressed is probably closer to the
truth). I can get the Visual Basic Editor to open if I reinstall Office
freshly and don't update at all, however, my macros won't actually run to
completion. The main applications will work fine for the most part, as long
as you don't need any macros. Any component that is listed as a type "shlb",
for shared library, is owned by another application. At first it was Python,
but I deleted that and then it was "Spark ME Shared Lib". I even tried
deleting the MacOSX version of the Desktop Database, but to no avail. So I
give. Anyone who claims that Office vX can work with Panther needs to give
me the Creator and Type codes for Visual Basic for Applications, otherwise,
no Brownie Points.

I'll be glad to upgrade if someone can assure me that I won't have issues
with Office 2004.

Oh, and Microsoft or Apple online support wasn't much help either. I looked.
They don't explicitly say that Office vX is compatible with MacOSX 10.3.x.

Thanks,
Jim

 

[Bob Greenblatt]

After much experimentation, I am convinced that the two are not compatible.
I would love to hear from someone who thinks otherwise, however, before you
pounce on the reply button, the problem I have is with the shared libraries
in Office such as Visual Basic for Applications, Microsoft Component Plugin,
MS OLE Automation (Carbon), etc. etc. They are not apparently owned by
Office due to conflicts with type/creator codes, even though MacOSX was
supposed to have "progressed" past them (regressed is probably closer to the
truth). I can get the Visual Basic Editor to open if I reinstall Office
freshly and don't update at all, however, my macros won't actually run to
completion. The main applications will work fine for the most part, as long
as you don't need any macros. Any component that is listed as a type "shlb",
for shared library, is owned by another application. At first it was Python,
but I deleted that and then it was "Spark ME Shared Lib". I even tried
deleting the MacOSX version of the Desktop Database, but to no avail. So I
give. Anyone who claims that Office vX can work with Panther needs to give
me the Creator and Type codes for Visual Basic for Applications, otherwise,
no Brownie Points.

I'll be glad to upgrade if someone can assure me that I won't have issues
with Office 2004.

Oh, and Microsoft or Apple online support wasn't much help either. I looked.
They don't explicitly say that Office vX is compatible with MacOSX 10.3.x.

Thanks,
Jim

Jim,

I can't give you type and creator codes; however, system 10.3.4 and office
2004 are completely compatible. I have been running them for quite a while
and have absolutely no compatibility problems. I am an Excel developer and
have no VBA problems. Did you completely remove all prior versions of office
using the remove office tool before installing office 2004? Did you repair
permissions before and after installing Office 2004?

 

[JE McGimpsey]

Anyone who claims that Office vX can work with Panther needs to give
me the Creator and Type codes for Visual Basic for Applications,
otherwise, no Brownie Points.

Not sure why I'd care about "Brownie Points", but the Type code for
Visual Basic for Applications is "shlb" and the creator code is "VBE_"
(where the underscore represents a space character, to avoid an
unfortunate line wrap).

I'll be glad to upgrade if someone can assure me that I won't have issues
with Office 2004.

Can't ever assure you of that. Can only assure you that I, and thousands
of other installations, don't. I'm a developer of cross-platform VBA
solutions, and I have had absolutely no OS-related incompatibility with
Office/VBA, with either Office v.X or Office 2004.

Oh, and Microsoft or Apple online support wasn't much help either. I looked.
They don't explicitly say that Office vX is compatible with MacOSX 10.3.x.

You're right that it's not explicit, but MS probably figures that

Operating System: Mac OS X version 10.1 or later

covers it (http://www.microsoft.com/mac/howtobuy.aspx?pid=sysreq).

 

[Jim Meador]

Not sure why I'd care about "Brownie Points", but the Type code for

Visual Basic for Applications is "shlb" and the creator code is "VBE_"
(where the underscore represents a space character, to avoid an
unfortunate line wrap).

Thank you. That answers my question. Since that is the creator and type
codes I see for each of these shared library files, I believe the problem is
with my system, which is connecting the files with the wrong application. I
just wish I knew how to fix it. As Bob asked, I fixed the permissions with
Disk Utility, and have never had the Demo version on my hard drive, but all
files that are essentially shared libraries in the Office directory are
listed in the finder as kind = "Spark ME shared library", which I think is
the reason why the VBA Editor won't fire up and I can't even use RealBasic.
I think I could fix the problem if I could attach an Office application to
the files with Xray, but that does not appear possible, since I can't find
an application to attach them to. There is no "Office Application". Also,
from what you have said below, I doubt upgrading to Office 2004 will fix
this issue. I will add this is the only application on my hard drive that
has any issues after installing a new hard drive and a clean install of
MacOSX 10.3 + the updates.

I really appreciate the input, however.
Thanks,
Jim

 

[Jim Meador]

Jim,

I can't give you type and creator codes; however, system 10.3.4 and office
2004 are completely compatible. I have been running them for quite a while
and have absolutely no compatibility problems. I am an Excel developer and
have no VBA problems. Did you completely remove all prior versions of office
using the remove office tool before installing office 2004? Did you repair
permissions before and after installing Office 2004?

Bob,

Thanks very much for your response. I did use the Office Remove tool before
installing Office vX (I don't have Office 2004) after things went awry. I
also fixed permissions, but I am still having problems.

What happened exactly is that I had to install a new hard drive in my
Powerbook G3 Pismo when one went dead. I had backups and so I dragged over
my updated Office folder to the new MacOSX Applications folder and
reconnected my old user folder via the Netinfo Manager (my user folder is on
a different partition to make backing it up easier. So my User folder and
all my document folders are on a separate partition from the MacOSX and
Applications partition). So after reconnecting my user folder and restarting
everything was back to normal, or seemingly so. When I went to use Word and
a macro I wrote in VBA, the macro wouldn't work, and then is when I went to
removing Office with the remove tool and reinstalling from the cd, then
tried it and the editor started up. So I applied the patches to Office,
10.1.2, then .4 then .5, and restarted. Then when I tried to open the VBA
editor, it wouldn't open. I went searching and found all these shared
libraries in the Office folder that appear to be claimed by a wrong
application in the Finder window and I can't figure out a way to rebuild the
desktop sufficiently or reattach the shared libraries to "Office". I can't
figure out how to fix this problem and so I guess I won't be able to use
macros anymore. Bummer. This may be what causes me to seriously look at Open
Office, however, my work uses Windows and Office, of course. I might add
that I am having no other issues with any of around a hundred other
applications I use. Just Microsoft Office VBA. Word, Excel and PowerPoint
work fine.

I very much appreciate your response. It is very helpful even if it doesn't
fix my problem.
Thanks,
Jim