SILAS and Word 2007 the easy way, avoiding "error in hidden module"
8 views
Skip to first unread message
JimH
Sep 15, 2010, 7:11:13 PM9/15/10
to silas-talk
A SILAS user has just written this to me, and I thought I'd put it
into the archives for this group, in case others have a similar
problem:
[-----
I have recently installed Office Word 2007. I have added SILAS as an
Add-in template with my Paratext rtf file open. This file was from My
Paratext Projects folder.
When I try to open a new language file from SILAS, I get the following
message in a Microsoft Visual Basic dialogue box:
Compile error in hidden module: Lang Data
What am I doing wrong?
-----]
I haven't worked with the user personally on this yet, but my guess is
that this comes from having an older version of SILAS on the computer
(before 2.208-1.06) and using a harder way of attaching the SILAS
template than is now available in Word 2007.
Word 2007 restricts macros that are loaded from templates that are in
non-standard places, and provides a way for you to tell it that the
non-standard place is trustworthy. This is a bit complicated to do, so
from version 2.208-1.06 of SILAS, the template Silas.dot is installed
to the folder where Word looks for User Templates. This is a trusted
place, so Word 2007 uses the SILAS features without complaining.
If you get the error that this user reports, here's what I suggest:
1. Close Word.
2. Open the folder My Paratext Projects and delete the file there
called "Silas.dot".
3. Download the latest version of SILAS from code.google.com/p/silas
and install it.
When you save a file as RTF from Paratext or TE, or open a previously-
saved RTF file, do these steps to attach SILAS:
a. Tap the Alt key and let it up again to display hotkeys.
b. Tap the X key to open the Add Ins tab.
c. Tap F or Y to run the macro to attach the SILAS template to the
file.
If that doesn't solve the problem, pls send a full error report, using
the item on the ScrLanguages menu (or if you can't run macros at all,
please report the version number of SILAS that you have installed) and
we'll interact on the issue.
The reason we don't add SILAS as an Add In is that we don't want it
attached to all files, just to Scripture files.
Jim
into the archives for this group, in case others have a similar
problem:
[-----
I have recently installed Office Word 2007. I have added SILAS as an
Add-in template with my Paratext rtf file open. This file was from My
Paratext Projects folder.
When I try to open a new language file from SILAS, I get the following
message in a Microsoft Visual Basic dialogue box:
Compile error in hidden module: Lang Data
What am I doing wrong?
-----]
I haven't worked with the user personally on this yet, but my guess is
that this comes from having an older version of SILAS on the computer
(before 2.208-1.06) and using a harder way of attaching the SILAS
template than is now available in Word 2007.
Word 2007 restricts macros that are loaded from templates that are in
non-standard places, and provides a way for you to tell it that the
non-standard place is trustworthy. This is a bit complicated to do, so
from version 2.208-1.06 of SILAS, the template Silas.dot is installed
to the folder where Word looks for User Templates. This is a trusted
place, so Word 2007 uses the SILAS features without complaining.
If you get the error that this user reports, here's what I suggest:
1. Close Word.
2. Open the folder My Paratext Projects and delete the file there
called "Silas.dot".
3. Download the latest version of SILAS from code.google.com/p/silas
and install it.
When you save a file as RTF from Paratext or TE, or open a previously-
saved RTF file, do these steps to attach SILAS:
a. Tap the Alt key and let it up again to display hotkeys.
b. Tap the X key to open the Add Ins tab.
c. Tap F or Y to run the macro to attach the SILAS template to the
file.
If that doesn't solve the problem, pls send a full error report, using
the item on the ScrLanguages menu (or if you can't run macros at all,
please report the version number of SILAS that you have installed) and
we'll interact on the issue.
The reason we don't add SILAS as an Add In is that we don't want it
attached to all files, just to Scripture files.
Jim
Reply all
Reply to author
Forward
0 new messages