Sage 100

 View Only
  • 1.  I still think it's odd that Sage's migration of sy

    Posted 03-28-2012 10:30
    I still think it's odd that Sage's migration of system files does not merge in the migrated company to any existing list of company files. For example - test 4.5 - these exist ABC ABX EEC MFG XYZ Migrate one company UPG and answer YES to system files and NO to migrate already existing Only UPG shows in the company maintenance post-migration. In understand (I think) what Sage is doing -- basically overwriting system files. But wouldn't the better route be to merge the incoming company code into an existing company maintenance list? It just seems lazy to me.


  • 2.  RE: I still think it's odd that Sage's migration of sy

    Posted 03-28-2012 10:32
    Why wouldn't those companies exist in the system files you're migrating - are they not in the installation you're migrating from?


  • 3.  RE: I still think it's odd that Sage's migration of sy

    Posted 03-28-2012 10:35
    No they aren't -- i often don't know what company codes are on an existing system so I setup a few just to be sure I can get into 4.5 and install fixes, patches, etc. I've found if you don't add sample data from the initial setup there is no way to get into MAS 4.5 -- unless I'm overlooking something.


  • 4.  RE: I still think it's odd that Sage's migration of sy

    Posted 03-28-2012 10:37
    Wayne, I always wondered that as well. Lazy coding it what I write it off to. My workaround is to go into Company Maintenance and create the companies. It will recognize the data files being there for the modules activated in that company and you are good to go.


  • 5.  RE: I still think it's odd that Sage's migration of sy

    Posted 03-28-2012 11:27
    I do that, too. It's done that for as long as I can remember.