Sage 100

 View Only
  • 1.  MAS 200 v4.05 data conversion to v4.50. Error 11

    Posted 07-11-2013 22:33
      |   view attached
    MAS 200 v4.05 data conversion to v4.50. Error 11 SO_levelconversion.pvc 1264 The customer does not use sales tax, everything is non taxable.


  • 2.  RE: MAS 200 v4.05 data conversion to v4.50. Error 11

    Posted 07-11-2013 22:38
    If you DFDM that file, is there anything there?


  • 3.  RE: MAS 200 v4.05 data conversion to v4.50. Error 11

    Posted 07-11-2013 23:01
    I did. It's all nontaxable data


  • 4.  RE: MAS 200 v4.05 data conversion to v4.50. Error 11

    Posted 07-11-2013 23:05
    Have you tried rebuilding that file in 4.05, and then bringing it over?


  • 5.  RE: MAS 200 v4.05 data conversion to v4.50. Error 11

    Posted 07-11-2013 23:35
    Yes. I rebuilt it in v4.05 and it rebuilt fine. Also rebuilt sorts. Not sure what is holding it up.


  • 6.  RE: MAS 200 v4.05 data conversion to v4.50. Error 11

    Posted 07-12-2013 05:10
    Is that 4.50.00 or a later PU of 4.50?


  • 7.  RE: MAS 200 v4.05 data conversion to v4.50. Error 11

    Posted 07-12-2013 06:31
    4.50.4


  • 8.  RE: MAS 200 v4.05 data conversion to v4.50. Error 11

    Posted 07-12-2013 06:57
    I think it's trying to write SO_SalesOrderTaxDetail file. Try the Debug, then ? fid(chndest) (Enter). That's the file it's trying to write.


  • 9.  RE: MAS 200 v4.05 data conversion to v4.50. Error 11

    Posted 07-12-2013 08:05
    Yes, when I run the debug it is pointing to the SO_SalesOrderTaxDetail file


  • 10.  RE: MAS 200 v4.05 data conversion to v4.50. Error 11

    Posted 07-12-2013 08:13
    Just a thought - have you tried to reinit/recreate the so_15 file? Can you copy a blank one from another company? Have you tried turning sales tax on and then converting?


  • 11.  RE: MAS 200 v4.05 data conversion to v4.50. Error 11

    Posted 07-12-2013 09:21
    no I have not but will. We are desperate at this point. This is a test upgrade that has been refreshed several times and I do not remember ever having this error before.