Sage 100

 View Only
  • 1.  I've got what I'm going to call...an interesting o

    Posted 09-25-2013 06:41
    I've got what I'm going to call...an interesting one. (MAS90 4.4) We designed a crystal report that is using WOS_TransEntryDetail that runs fine from their server. When the users try to run it they get an unknown field message. If we open the report in Crystal Reports on the workstations and verify the database the fields in WOS change.(they seem to be incorrect bad field names, etc.) Seems to be a Data Dictionary issue that shows up on the workstations. ideas?


  • 2.  RE: I've got what I'm going to call...an interesting o

    Posted 09-25-2013 06:45
    Reinstall the workstation? Seems odd that all of them have it.


  • 3.  RE: I've got what I'm going to call...an interesting o

    Posted 09-25-2013 06:51
    @JeffSchwenk. I know that was my thought. I tried that on one workstation, no luck. We have only checked 2 workstations and they are both messed up.


  • 4.  RE: I've got what I'm going to call...an interesting o

    Posted 09-25-2013 07:01
    Standard or advanced, Service Update? What if you uninstall the WS client, then reinstall? Where was the report written - On their server or at your office? Grasping at straws here.


  • 5.  RE: I've got what I'm going to call...an interesting o

    Posted 09-25-2013 07:23
    It's standard. Service update is way behind. I'll try uninstalling WS client first. Report was written directly on their server. I tried starting a new report on their workstations and the table fields are wrong there too. That's a good thought though, I'll pull the report and see what it does on my system.


  • 6.  RE: I've got what I'm going to call...an interesting o

    Posted 09-25-2013 14:45
    You may want to redo drive mapping too, since it's standard.


  • 7.  RE: I've got what I'm going to call...an interesting o

    Posted 09-25-2013 14:53
    Interesting. Might explain why server works.