From 4a090ba06a54f5da179ac02bb307cc03d08831bf Mon Sep 17 00:00:00 2001 From: Gerald Carter Date: Wed, 16 Jul 2003 05:34:56 +0000 Subject: trying to get HEAD building again. If you want the code prior to this merge, checkout HEAD_PRE_3_0_0_BETA_3_MERGE (This used to be commit adb98e7b7cd0f025b52c570e4034eebf4047b1ad) --- docs/faq/FAQ-ClientApp.html | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-) (limited to 'docs/faq/FAQ-ClientApp.html') diff --git a/docs/faq/FAQ-ClientApp.html b/docs/faq/FAQ-ClientApp.html index 3f680b78d7..6e37fbcba5 100644 --- a/docs/faq/FAQ-ClientApp.html +++ b/docs/faq/FAQ-ClientApp.html @@ -1,5 +1,4 @@ - -Chapter 4. Specific client application problems
Chapter 4. Specific client application problems
Prev   Next

Chapter 4. Specific client application problems

Table of Contents

MS Office Setup reports "Cannot change properties of '\\MSOFFICE\\SETUP.INI'"
How to use a Samba share as an administrative share for MS Office, etc.
Microsoft Access database opening errors

MS Office Setup reports "Cannot change properties of '\\MSOFFICE\\SETUP.INI'"

+Chapter 3. Specific client application problems

Chapter 3. Specific client application problems
Prev   Next

Chapter 3. Specific client application problems

Table of Contents

MS Office Setup reports "Cannot change properties of '\\MSOFFICE\\SETUP.INI'"
How to use a Samba share as an administrative share for MS Office, etc.
Microsoft Access database opening errors

MS Office Setup reports "Cannot change properties of '\\MSOFFICE\\SETUP.INI'"

When installing MS Office on a Samba drive for which you have admin user permissions, ie. admin users = username, you will find the setup program unable to complete the installation. @@ -11,14 +10,14 @@ rdonly by trying to open it for writing. Admin users can always open a file for writing, as they run as root. You just have to install as a non-admin user and then use "chown -R" to fix the owner. -

How to use a Samba share as an administrative share for MS Office, etc.

+

How to use a Samba share as an administrative share for MS Office, etc.

Microsoft Office products can be installed as an administrative installation from which the application can either be run off the administratively installed product that resides on a shared resource, or from which that product can be installed onto workstation clients.

The general mechanism for implementing an adminstrative installation involves -running X:\setup /A, where X is the drive letter of either CDROM or floppy. +running X:\setup /A, where X is the drive letter of either CDROM or floppy.

This installation process will NOT install the product for use per se, but rather results in unpacking of the compressed distribution files into a target @@ -45,8 +44,8 @@ set the following parameters on the share containing it: browseable = yes public = yes

  • Now you are ready to run the setup program from the Microsoft Windows -workstation as follows: \\"Server_Name"\MSOP95\msoffice\setup -

    • Microsoft Access database opening errors

    +workstation as follows: \\"Server_Name"\MSOP95\msoffice\setup +

    Microsoft Access database opening errors

    Here are some notes on running MS-Access on a Samba drive from Stefan Kjellberg

    Opening a database in 'exclusive' mode does NOT work. Samba ignores r/w/share modes on file open.
    Make sure that you open the database as 'shared' and to 'lock modified records'
    Of course locking must be enabled for the particular share (smb.conf)

    -

    Prev Up Next
    Chapter 3. Configuration problems Home Chapter 5. Common errors
    +

    Prev Up Next
    Chapter 2. Compiling and installing Samba on a Unix host Home Chapter 4. Common errors
    -- cgit