On occasion customers have asked us about configuration changes on a
network (using the Tools-Configure command in Lexwin) that don't seem
to make changes elsewhere on the network. For example, you may want to
configure an "alternate database" to be a file of new books or videos.
Let us say its located at f:\applications\lex\new.file

You have a problem here, when you make a configuration change it saves
to a file (Lexwin.ini) on the local hard drive. That makes your
configuration change unavailable on other stations. This is good in
some ways; your library workers at different terminals can have
customized programs. The downside is that you cannot make features
available over many network terminals by making one quick change.

This should be an area for Lexwin to develop. We likely need to have
two configuration files, a default one for the whole network and a
separate one for the local station that records "differences from the
local configuration" Such as local printers, etc.

Here is our programmers analysis of the situation, with a few comments
of my own entered in for clarification. Some of the information may
require a network administrator's interpretation for you.
______________________________________________________________
There is no provision for changing the default database name globally.
It has to be done at all workstations individually but maybe the
following will show you some shortcuts.

Lexwin looks for the default database name in the following order:
command line argument
local \windows\Lexwin.ini <Click on START-Search-Files and Folders
And search local hard drives for Lexwin.ini>
Lexwin.ini in the Lexwin program directory
<Use explorer to search the Lexwin program
directory found in your View-System
report>
lexcfg.cfg in the current working directory (from a previous LEXIFILE
install) lexcfg.cfg in the Lexwin program directory (from
a previous
Lexwin install)

Lexwin does not generate a Lexwin.ini in the program directory
anymore, but earlier versions used to so it still looks for one there
in case this is an upgrade from an early version. That could be used
to advantage by copying a Lexwin.ini there and then deleting the local
\windows\Lexwin.ini files. Lexwin will then copy the program
directory Lexwin.ini to the local \windows directories.

Another solution, edit the \windows\Lexwin.ini files and put the
correct default database in main= in the [desktop] section. Even if
the user does not have a password to change the default database in
Lexwin, they can do the same by editing the \windows\Lexwin.ini file
manually. Maybe this should not be made known to all users. A
corrected Lexwin.ini could even be copied to other workstation
\windows directories.

A problem with copying Lexwin.ini from one computer to another is that
other defaults may be copied that do not apply to the workstations,
like default printers. That could stop printing from working or even
crash the program until the default printer is corrected.

Another suggestion, use network pathnames instead of mapped pathnames,
\\lexserver\lex\loc.fil instead of N:\lex\loc.fil in case all
workstations are not mapped the same. In your case they probably all
are the same.