Sage 100

What do you do unique for folder layouts for MAS90? With my upgrades I always add in a \CONSULTANT folder where I store all sorts of upgrade specific files. Do you have a folder structure that you follow? I'm starting to navigate toward: \SAGE \SAGE\MAS90\ \SAGE\MAS90\CONSULTANT \SAGE\MAS90\CONSULTANT\DOWNLOADS \SAGE\FRX \SAGE\PAPERLESS \SAGE\SOURCE DISKS A while back I used to stick everything into a subfolder below WKSETUP until the upgrades started to wipe that folder. I'm gradually gathering tools that I find I need on every implementation. I think I'm going to stick them on a USB 32 GB drive and bring them with me and also mirror them online. Tools: - Crystal calendar fix promptengine_calendar.js - vcredist_x86.exe (fix PvxDAX issues) Other thoughts?

We have a Sage folder but below that are folders for the version. E.g. Sage\Version440, Sage\Version450, etc. Also a paperless folder, and an Install folder. Sometimes other folders.

We don't put anything inside the MAS90 folder but we usually have a Download or Install folder under the Sage directory.

I have a BLSReports folder at the same level as MAS90 folder. Depending on the complexity of the install, I may have subfolders under it. I also have a ...MAS90\reports\Custom folder where I install any Custom Crystal reports before I add them to the MAS menu. This is in addition to the BLSReports folder for Crystal. My FRx Sysdata folder is structure similarly to what you have. I have a product updates folder for all PUs for that version also. I keep my paperless under the MAS_XXX folder for back up purposes but I am rethinking that stategy as I install v4.5. Not sure what the best place for it is yet. In addition to locating it where the IT department will back it up, I also bury it deep in the structure to keep wondering eyes from exploring. Some clients have set up a separate PR folder for paperless and have restricted access to the folder via network rights.

@JeffSchwenk we no longer have the paperless in the MAS90 directory due to the fact that you have to move everything when you upgrade. If you keep it at Sage\Paperless, the mapping is still correct. In addition, if you are copying the MAS90 directory as a backup, those paperless files can take a LONG time! We also have a Reports directory under Sage for any modified reports/forms as a backup.

Am considering also a \SAGE\READMEFIRST for IT folks --- however I am guessing hardly anyone will read ...

I like everything under one folder - such as \SAGE because it's easy to tell the IT folks to drag/drop \SAGE and all subfolders to make a backup. Whether they listen is another matter.

If always started with \90w and have an updates folder under it. I wasn't planning on renaming it \100w and hope that doesn't violate my partner agreement. I wonder if sage marketing will convince engineering to change the install folder to Sage100 rather than MAS90.

We have a standard naming convention in the customer environment. Start with the client name. Under that have separate Sage\MAS 90 and Documents folders to segregate Paperless and other documents for security purposes. We have a transfer folder where we have sub-folders for installs, patches, and backups for migrations. I think it is like any other methodology.... find one that works for you and then stick with it religiously.

@ThereseLogeais - I agree on all points. I just like having it under the company data folder so it is never overlooked during backup. As I install v4.5, I'll probably change my strategy.

We use a parent folder just under the server share point (often APPS) named with the product and version (MAS20045). On some newer systems, I have been inserting a Sage Folder between the Share and the parent folder. Within the parent folder, we have the MAS90 folder plus folders for year end, product updates and hot fixes, reports backup, documentation, notes, ect. We don't put anything in the MAS90 folder. Paperless data is usually put at the same level as the MAS parent folder. When we can, convenience items such as install CD copies and install images get stored in a separate Drive/Partition that does not get backed up.

Sage is now the share folder - I abbreviate Version to keep the number of characters down so as to not hit the 30 character limit on report manger F:\Sage\Ver440\MAS90 F:\Sage\Ver450\MAS90 F:\Sage\Ver440\Patches F:\Sage\Paperless - at a high level so that when you do a new version you do not need to move the pdfs. But then I do break out paperless into companies if they have multicompany, registers, then modules. F:\Sage\Frx