Laith;
Keep everything on the server and keep all of the printer, drive mapping
and directory structures consistent. We operate over a 100BaseT network
without trouble, unless someone starts bending the "rules" on how tables
are created named, stored, etc. To develop our "rules" we outlined how data
would be used and then established guidelines for content, format and file
naming. This works most of the time.
Best regards,
Bruce B. Blais
Principal Consultant
PCN Professionals, Inc.
Wireless Telecom Specialists
Richardson (Dallas), Texas USA
www.pcn-pros.com
-----Original Message-----
From: Laith Wark [SMTP:[EMAIL PROTECTED]]
Sent: Friday, October 22, 1999 00:26
To: MapInfo List Serve (E-mail)
Subject: MI Housekeeping
A housekeeping question.
Can anybody suggest an orderely and efficient way of storing tables and
workspaces over a network with the aim to:
1. Maintain workspace robustness
2. Reduce the amount of space taken
3. Enable the fastest working speed
With the amount of dud workspaces failing to open due to corrupted paths, I
resorted to making copies of each table, and saved it in the same folder as
the .wor. Needless to say, this uses a LOT of space (ok, I went for the
"fix it with a hammer" approach).
Any advices would be appreciated.
Laith
========================================
Laith Wark
EDAW (Aust) P/L
Design, Planning and
Environments Worldwide
Level 4 Rowes Building
235 Edward Street
Brisbane 4000
Australia
Ph: INT +61 (0)7 3229 6422
Fx: INT +61 (0)7 3229 6422
Email: [EMAIL PROTECTED]
========================================
----------------------------------------------------------------------
To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put
"unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
----------------------------------------------------------------------
To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put
"unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
