Sage 100

 View Only
Expand all | Collapse all

Do newer versions of Sage 100 ""Standard"" need to r

  • 1.  Do newer versions of Sage 100 ""Standard"" need to r

    Posted 03-23-2016 11:32
    Do newer versions of Sage 100 ""Standard"" need to run from a mapped drive any more? The install manual still says a mapped drive is required under the Windows 2003 section. However, it seems that even if your install from a mapped drive Windows typically replaces it with a UNC. Most don't notice the change it seems to work fine. I would love to stop going to the properties of the shortcut and replacing the UNC with a mapped drive letter. @Sage100Routine


  • 2.  RE: Do newer versions of Sage 100 ""Standard"" need to r

    Posted 03-23-2016 11:41
    I always use a UNC anymore, I am thinking maybe since 4.4?


  • 3.  RE: Do newer versions of Sage 100 ""Standard"" need to r

    Posted 03-23-2016 11:43
    I've been using UNC without issue.


  • 4.  RE: Do newer versions of Sage 100 ""Standard"" need to r

    Posted 03-23-2016 11:53
    I still use mapped drive, but in the cases where it converts to a UNC path in the icon, I just leave it. Haven't had any problems.


  • 5.  RE: Do newer versions of Sage 100 ""Standard"" need to r

    Posted 03-23-2016 11:58
    I believe the mapped drive was used by Crystal reports. It could be the newer versions of Crystal don;t need the mapping any more. In older versions, if there wasn;t a mapped drive in the ODBC driver then Crystal couldn't find the data.


  • 6.  RE: Do newer versions of Sage 100 ""Standard"" need to r

    Posted 03-23-2016 12:11
    Do you all now install from a UNC, or do you still start with a mapped drive?


  • 7.  RE: Do newer versions of Sage 100 ""Standard"" need to r

    Posted 03-23-2016 12:16
    From a UNC, use Autorun.exe, run as Admin. That's my mantra.. .LOL


  • 8.  RE: Do newer versions of Sage 100 ""Standard"" need to r

    Posted 03-23-2016 12:34
    I have been using a mapped drive, however, I also noticed recently that it doesn;t seem to matter anymore. I am not sure if there has been any official word from Sage. It would be nice to know if we are wasting time creating mappings or having the IT people push out mappings from group policy. Great question Bill.


  • 9.  RE: Do newer versions of Sage 100 ""Standard"" need to r

    Posted 03-23-2016 15:24
    Officially at Sage, and I was there for this, mapped drives were no longer required since a version 4.20 product update. That's when Vista support for MAS came along and UNC had to be supported as part of a Microsoft requirements for developers supporting Vista. Vista is a thing of the past but UNC is still fine. However I have seen twice where loading a screen like S/O Entry in MAS 90 (Sage 100 Std) was taking 10 - 15 seconds and all the standard culprits like A/V, switch, etc were not in play. It turned out these networks had DNS issues and so executing a UNC path was resolving to the IP very slowly ergo the slow screen load. Experimented with a mapped drive and it was fast. It was easier to change the shortcut than trying to explain the issue. This is just the exception scenario of course.


  • 10.  RE: Do newer versions of Sage 100 ""Standard"" need to r

    Posted 03-23-2016 15:24
    Perhaps we should do a poll???


  • 11.  RE: Do newer versions of Sage 100 ""Standard"" need to r

    Posted 04-20-2016 05:52
      |   view attached
    May be prudent to still use mapped drives. It may prevent a future headache.

    Attachment(s)



  • 12.  RE: Do newer versions of Sage 100 ""Standard"" need to r

    Posted 04-20-2016 07:02
    Until Windows loses the mapping...use IP address in the UNC to eliminate DNS delays


  • 13.  RE: Do newer versions of Sage 100 ""Standard"" need to r

    Posted 04-20-2016 07:13
    Note that Sage Intelligence won't work with a mapped drive. UNC is required.


  • 14.  RE: Do newer versions of Sage 100 ""Standard"" need to r

    Posted 04-20-2016 08:15
    If the client has DNS problems, using a UNC may be slow. A mapped drive should solve that problem.