Sage 50 question.

Soldato
Joined
26 May 2009
Posts
22,174
Does anybody know if you can install Sage Line 50 on a standalone machine, then change to a network install afterwards? And if so how much agro it is? Thanks.
 
I think that the location of the sage database is located in program files when it is standalone in an accounts000 folder or similar. You could share this folder out on the network, or copy this database to a server or Nas.

I think there is a txt file stored somewhere with the location of the database written in plain text. I think you can edit that file to point it to the new location.
 
just had a look, and in sage accounts 2014 ( I assume you meant accounts, not payroll/HR etc.), you can go to

File > New > Company

and then select existing company, and add it in as you would at the time of installation.
 
Should be pretty straightforward, I know it is for Sage 50 Payroll as I've done it. Just a case of moving the files to the server and pointing the program to the new path. Can't imagine its that different for Line 50
 
There is a company.dat text file that contains the locations of any datasets you may have. You can edit this file directly or there is a way to do it through the gui, in older versions it was located in the Sage Accounts program directory but on new version is it somewhere like C:\Program Data\Sage\Accounts I believe.
 
If this is for accounts?

All you need to do is copy the company.000 folder to where ever you want. Then go to c:\programdata\sage\accounts\2014\

Replace 2014 with whatever year your Sage is and then open a file called company in notepad. This contains the path to the Sage data so just replace this with the network share name or map the drive to the network share and map it via the drive letter.
 
The latest version of Line 50 I saw last week introduces Windows services into the mix.

Two Sage services needed to be installed / run on the server hosting the Sage accounts folder and the SYSTEM account the services were running under needed to have read/write priv's to the Sage folders.

Sage on the client PC then talks to the services.
 
The latest version of Line 50 I saw last week introduces Windows services into the mix.

Two Sage services needed to be installed / run on the server hosting the Sage accounts folder and the SYSTEM account the services were running under needed to have read/write priv's to the Sage folders.

Sage on the client PC then talks to the services.

This is true and not a problem for a small business so long as it is mapped via UNC path. The new version has also had a new feature already disabled as it wasn't ready.
 
Back
Top Bottom