🚀 go-pugleaf

You definitely should split up the application as recommended in the reply,
and follow the scheme to use local copies of the front-end user interface
attached to a back-end data module situated on the network.  The problem
with placing the whole application on the network, as opposed to just the
data, is that the network traffic increases tremendously with the entire
app being run from the network, since the "wire" must carry all of the
query, form, report, module, and macro information to each workstation each
time the user accesses one of those components; so every time you run a
query, for example, Access must download the whole query into the local
workstation as well as the data.

Make sure the Novell setup allows for maximum number of locks allowable. 
You really don't need to use replication, just provide the latest design of
your app as a network download for users to update their workstations as
needed.  Replication is more suited to multiple data locations than it is
for multiple front-end locations, although it can accomodate that too.
-- 
Pete B

Richard Steckis <rsteckis@fish.wa.gov.au> wrote in article
<01bd1405$997add40$4102a8c0@S137838.fish.wa.gov.au>...
> It does'nt really matter what LAN system you are using (we use Banyan
> Vines), the trick is to separate your database into two.  One database
> holds just the tables and data.  This is the database that you install
> permanently on the network and is known as the backend database.  The
other
> database holds all the forms, queries, reports etc and is known as the
> front end database. A copy of the front end database can reside on either
> the network drive or on any work station hard drive.  You attach the back
> end tables to the front end database and bob's your uncle you can have 20
> people accessing the same data tables from their work stations with the
> front end database installed on the work station hard drive.
> 
> The beauty of this system is that the corporate data resides on the
network
> and you can continue to develop your application from your own work
station
> or home computer.  When you install an upgrade of you application, always
> ensure that the attachment paths are correct.  Also ensure that when you
> open the backend database for the first time you disable the exclusive
> access check box.  I would only use replication for out of office use not
> the other way around.  The main database should always reside on the
office
> network. 
> 
> Hope this helps.
> 
> David Wresinski <david@catterton.com> wrote in article
> <683rbb$lr6$1@gte2.gte.net>...
> > I have developed a rather large database that can be used in my job.
> > The company I work for uses a Novell LAN. I have no experience in
> > LAN/WAN.
> > 
> > The problem...The company can now see the benefit of my program and
> > wants to put it on the server so other office personnel can use it.
> > Since I would want to keep the Design Master on my desktop at home,
> > could I just:
> > 
> > 1. Using Replication Manager, create the Design Master and Replica,
> > and upload the Replica to the server, then install Office 97 DE Tools
> > on the server, then create addtional replica's from the copy on the
> > server.
> > 
> > 2. Would I be able to syncronize from the Design Master at home to the
> > Replica on the server at work thru the internet?
> > 
> > 3. How involved would this get? Is there a sequence of steps somewhere
> > that one could follow. Online Help talks about Replication under MS
> > SQL Server and Windows NT but the office uses Novell.
> > 
> > 4. Would the office need to bring in a contract LAN/WAN guy. 
> > 
> 
>