I've experimented with things like that but have never gotten them to work. When I was experimenting I probably didn't exhaust all possible options, but I'm assuming the RS staff have. If there was a way to separate Office Automation from the Office folder it definitely would have been in their interest to do so.
I seem to remember from many years ago that someone at RS said the problem was the restrictive way Microsoft implemented the Automation Server. (I've slept since then so I could be remembering this incorrectly.) Greg --- Tim Jones <[EMAIL PROTECTED]> wrote: > On Mar 13, 2007, at 9:57 AM, Greg Kraus wrote: > > > It's actually because your application has to be > in the same folder as > > the Microsoft Office Automation libraries which > are included in MS > > Office. That is what is stored in the "Office" > folder in MS Office. > > Whenever an RB application is compiled to a format > that produces a > > bundle, your actual application file does not > reside in the Office > > folder - it now resides in a sub-folder within the > bundle inside the > > Office folder and thus cannot get access to the > Automation libraries. > > (At least that's my understanding of it.) > > Just as an experiment, what happens if you copy the > office automation > libraries into your app's Contents/MacOS/ folder? I > don't use > Office, so I can't answer that one myself. > > Tim > -- > Tim Jones > [EMAIL PROTECTED] > _______________________________________________ > Unsubscribe or switch delivery mode: > <http://www.realsoftware.com/support/listmanager/> > > Search the archives: > <http://support.realsoftware.com/listarchives/lists.html> > _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
