I've done it twice.

It takes planning, but it's not as bad as some may expect. It's really a
matter of ensuring that
you don't forget anything, such as AFI rules, customer/supplier control
accounts and so on.

On both occasions I converted history too and with a methodical approach
it's not bad.
Allow a weekend for the conversion routines to run.

Garry Clarke
Director
Bluetech Ltd
+353 86 2710 491


-----Original Message-----
From: system21-bounces@xxxxxxxxxxxx [mailto:system21-bounces@xxxxxxxxxxxx]
On Behalf Of John.Mcpherson@xxxxxxxxxxxxxxxx
Sent: 18 May 2005 15:45
To: system21@xxxxxxxxxxxx
Subject: [SYSTEM21] Calling all GL Experts

OK....Do not ask my why, but we have a request from our French sub to change
their chart of accounts.  They are currently setup with 1 level and
1 extension code level.  They would like to change this to be 2 chart of
account levels and no extension code levels.  My questions are therefore:

1. What is the best way to do this?
2. What effect will this haveon existing data?
3. When should we do this?  Would it be something that should only be done
at year end or can it be done in the middle of the year?
4. What happens if I switch off extension codes anyway?  Will this mess
anything up (even if I do not add the extra level)?
5. Anyone done it and what she we watch out for and what would the steps be?

Thanks for all the help.

Cheers,
John

_______________________________________________
This is the System 21 Users (SYSTEM21) mailing list To post a message email:
SYSTEM21@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/system21
or email: SYSTEM21-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/system21.


This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].