Thanks for that it also helped me with moving over my Access Data Backend But When running reports in sage it takes ages to do, where as it would only take 20 secs or so before it now takes 5 minutes, watching the packets move around it's as if the whole data is being moved over before the report previews, any idea's
Liam -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Louis Sabet Sent: 10 June 2003 12:42 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: Sage Line 50 Version 9 --On Saturday, June 07, 2003 11:27:32 +0100 [EMAIL PROTECTED] wrote: > Currently I have Sage Line 50 installed on a client PC and shared amongst > others via this, but I would like to install it on the RH9 Dell Server, > anyone done this or have any pointers how to do it ? > > Liam Hi Liam, I just battled through this myself - it wasn't easy. Mostly because of a lack of information on this specific problem out there, but the solution is relatively simple. (The trick is to look for info on file locking and MS Access databases). I presume you're currently running it on a windows machine, and want to instead store the data on SAMBA under linux. Step1: Install Samba (If you haven't already) Step2: Set up your smb.conf how you want it Step3: Create a SAGE share in the smb.conf like this: [sageline50] path = /home/netapps/sageline50 writeable = yes browseable = no create mask = 0777 directory mask = 0777 veto oplock files = /*.mdb/*.MDB/*.ldb/*.LDB locking = yes share modes = yes ...obviously replacing the path and share name above as appropriate. I found this worked well for me - you'll want to do some tweaking, specifically with permissions to stop people fiddling with things they shouldn't, but at least it works :-) Step4: chkconfig smb on (if you haven't already) Step5: /etc/rc.d/init.d/smb start (if you haven't already) Step4: Copy your sage data files from the windows machine to the samba share you just created Step5: Map drives from your windows clients to the new samba share (you'll need to ensure that usernames are the same on the client and redhat server). If you don't have users on the server (and don't want to), you can always set up the above share as a public share. You'll need a line like: guest user = ftp ...under the [general] section in smb.conf, and you'll want to add the line: public = yes ...to the share definition shown above. Step6: Change the Sage shortcuts on the windows machines so that the target is specified as: c:\path\to\sage\sfw.exe x: ...where x: is the drive letter you used to map to the sage data on your redhat server. The crucial lines in smb.conf for sage are: veto oplock files = /*.mdb/*.MDB/*.ldb/*.LDB locking = yes share modes = yes I found that unless these were in there, Sage would only allow access to one user at a time. Best Regards - feel free to contact me off-list if you need anything further. L -- Louis Sabet - IT Manager http://www.mobiles.co.uk http://www.gadgets.co.uk -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
