| Title: | ALL-IN-1 (tm) Support Conference |
| Notice: | Please spell ALL-IN-1 correctly - all CAPITALS! |
| Moderator: | IOSG::PYE CE |
| Created: | Fri Jul 01 1994 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 2716 |
| Total number of notes: | 12169 |
all-in-1 3.1 to 3.2
Have there been any changes to the NETWORK.DAT?
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2592.1 | IOSG::PYE | Graham - ALL-IN-1 Sorcerer's Apprentice | Wed Apr 02 1997 18:24 | 6 | |
<<<< all-in-1 3.1 to 3.2
What's 'all-in-1'??
There were no changes to NETWORK.DAT in ALL-IN-1 V3.2, or indeed in
V3.1, or V3.0, or.....
| |||||
| 2592.2 | IOSG::MARSHALL | Thu Apr 03 1997 18:46 | 14 | ||
The file format hasn't changed in the base product, but people often get caught out by site customisations, eg extending the length of the NETWORK field. Such customisations are supported as long as all the NETWORK.DAT files that are 'synchronised' (via smnetupdt) have the same record size and format. Problems occur if trying to access a NETWORK.DAT file on a remote system that has a different record size to that on the local system. This is completely unrelated to ALL-IN-1 version, although version mismatches are usually what people erronesouly assume is the problem. See topic 438 in this conference. Scott | |||||