DataPerCompany

vasam

We have existing system: one database with several companies and DataPerCompany set to 'No' for the table G/L accounts. The customer will keep only one company in the system operational and add one more but with separate g/l accounts. Is it ok to change the DataPerCompany setting and what might be the consequences?

einsTeIn.NET

No, that's not ok.

crisnicolas

On standard NAV, DataPerCompany is set to Yes.
If it is set to No on your database, that is because someone made that on purpose. We cannot say there will be no consequences, because if this has changed, there may exist some other modifications that rely on that...

rhpnt

If there are no other "modifications" there will be no consequences except that the setting is going back to "normal". But consider that before you can change this setting the table must be empty!

DenSter

einsTeIn.NET wrote:

No, that's not ok.

Then again, setting that property for the G/L Account table in the first place was not OK.

vasam

i guess for consolidation purposes they wanted to keep the same g/l codes. now there will be only one company left from previous and one new with different g/l codes. one solution is to create new db with separate objects. they will also need separate license instead of increasing the number of users on existing one.

rhpnt

vasam wrote:

i guess for consolidation purposes they wanted to keep the same g/l codes. now there will be only one company left from previous and one new with different g/l codes. one solution is to create new db with separate objects. they will also need separate license instead of increasing the number of users on existing one.

Well, first you have to know why that table was changed initially and what the customer really wants in the future. Nontheless, the table should be set to "per company" and consolidation should be made the NAV way (separate cons. company).

David_Singleton

vasam wrote:

We have existing system: one database with several companies and DataPerCompany set to 'No' for the table G/L accounts.

:shock: [-X

Amazing what people will do.

So now you can create a new company, with no transactions. Then close the year out, then go and randomly delete GL accounts. Sounds like fun.

vasam

our approach is to create new db and company in order to avoid problems with existing modifications.

David_Singleton

vasam wrote:

our approach is to create new db and company in order to avoid problems with existing modifications.

=D> =D> =D> =D>

Great decision.