From 293421f3c64a2adff7dc15f7ad3adb6120c9fd16 Mon Sep 17 00:00:00 2001 From: Gerald Carter Date: Wed, 24 Sep 2003 15:05:22 +0000 Subject: syncing up docs, examples, & packaging from 3.0 (This used to be commit dd1348c566b4700ea01bd89639e2d3330c878167) --- docs/faq/FAQ-ClientApp.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'docs/faq/FAQ-ClientApp.html') diff --git a/docs/faq/FAQ-ClientApp.html b/docs/faq/FAQ-ClientApp.html index 6ba4b1d36c..77e65c9f58 100644 --- a/docs/faq/FAQ-ClientApp.html +++ b/docs/faq/FAQ-ClientApp.html @@ -1,4 +1,4 @@ -Chapter 3. Specific client application problems

Chapter 3. Specific client application problems

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

+Chapter 3. Specific client application problems

Chapter 3. Specific client application problems

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. @@ -10,7 +10,7 @@ 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 @@ -45,7 +45,7 @@ set the following parameters on the share containing it: 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

    +

    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)

    -- cgit