Hi All,
We have found that the latest version of Lexis' Full
Authority software (v. 7.10.003.003) is in compatible
with Word XP. The problem is that when one is in a
Word XP document and invokes Full Authority, Word XP
freezes (this is the short explanation).
Below is a detailed explanation from our systems
integrator which will tell you more than you really
want to know, but I thought 1) some of you might like
a heads-up; 2) maybe LexisNexis might like a heads-up;
and 3) that maybe someone has had this problem before
and knows a workaround. By the way West's Citelink
3.01 product does work with these two programs. I
would appreciate knowing your experience with
Citelink's table of authorities capabilities.
Thanks for any info.
Lisa Baker
Musick, Peeler & Garrett LLP
Detailed explanation of the problem:
Using Microsoft Word 2002 (XP) with IManage DeskSite
6.01a and Full Authority 7.10.003.003 (the latest
update, #3, available on the Lexis-Nexis website), we
encountered the following problem:
When you open a pleading, either an iManage document
or a local document (even the Brief.doc supplied by
Lexis-Nexis for testing purposes) into Word, then
click the Full Authority button in the toolbar
supplied by Full Authority, the following occurs:
1. It closes your document and launches Full
Authority, as it should.
2. When you click OK on the Full Authority window,
it opens your document in Word "behind the scenes" and
saves it as an RTF file. This also is normal.
However, the RTF file remains open (you can see it in
the Windows taskbar) and the Full Authority "please
wait..." message remains there indefinitely.
3. You have to launch the Task Manager
(Ctrl+Alt+Delete) and End Task on the RTF document
(which is shown as "Not Responding").
4. You then have to click on the Full Authority
window. At this point, Full Authority issues the
following error message: "Invalid procedure or
function call."
5. When you click OK on this message, it proceeds
to scan the RTF file, create the TOA output (report)
file, reopen your pleading and open the TOA file into
Word, as it normally should.
So it actually completes the process, but only after
you have ended task on the RTF and OK'd the error
message.
If you launch Full Authority independently of Word (by
selecting the program icon, not the toolbar button
inside Word), the process works as it should, without
error.
After several discussions with Full Authority
representatives, they acknowledged having problems
integrating both with current versions of iManage AND
with Word XP. Today (5/2/02), they theorized that
Full Authority is having a problem when launching an
instance of Word to reopen your pleading and save it
as an RTF file if Word already is running, but after
some experimentation, I believe the problem lies
elsewhere. I have been able to create a macro that
launches Full Authority from within Word using the
Shell command (instead of the ShellWait command they
use), and it works just fine, even though Word already
is running. The catch is that using this command is a
bit like running Full Authority independently, because
when Full Authority is done creating the TOA, the
macro has ended and the TOA is not opened. I have to
launch a separate macro I created to open the TOA file
(which I insert directly into the original pleading).
I have not been able to run the entire process using a
single macro, as we desire and they intended.
__________________________________________________
Do You Yahoo!?
Yahoo! Health - your guide to health and wellness
http://health.yahoo.com
This archive was generated by hypermail 2b29 : Wed Nov 14 2007 - 20:36:32 PST