Sage 100

 View Only
Expand all | Collapse all

Error adding UDF To AR_InvoiceHistoryHeader sourced. Error 65 CMWUD2 line 9040

  • 1.  Error adding UDF To AR_InvoiceHistoryHeader sourced. Error 65 CMWUD2 line 9040

    Posted 04-02-2021 15:50
    This is the second client that I've had this issue in v2020 Premium

    I'm trying to add a UDF to AR_InvoiceHistoryHeader and have it sourced with the business object of SO_SalesJournal_upd.  As soon as i select the business object (either from the Data Sources tab or from the Attribute tab, the Error 65 in program CMWUD2 at line 9040 appears.

    I've attached a screen shot of the error for a visual.  If I click info and try to print the error listing, it goes to a providex prompt.

    I had this case created at the end of January and after a couple of hours on the phone with Sage demonstrating the problem, Sage Support advised to install PU1.  The client didn't want this done as they were in the midst of business season.  Sage conveniently closed the case and marked it resolved, even though it clearly wasn't.

    I tried again today on another client system, v2020 Premium with PU1 installed and the identical error happened.  So, clearly the PU wouldn't have fixed the first client either.  Both clients have third party enhancements; the only common one is Scanforce, but I can't imagine that has anything to do with custom office errors.

    Has anyone had this error and been able to resolve it successfully?  I'll send to Sage again, but frankly, I'm losing faith in their ability to resolve clear program issues on a timely basis.

    Note - I can add UDF if it's not sourced from a business object, but since it's history, definitely need it sourced.

    Thanks in advance, Robert



    ------------------------------
    Robert White
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------


  • 2.  RE: Error adding UDF To AR_InvoiceHistoryHeader sourced. Error 65 CMWUD2 line 9040

    Posted 04-02-2021 16:06
    I was able to move forward by creating the same UDF on my local providex 2020 PU1 system and export from my local and import to the client's system.

    The UDF importing successfully and the flow is working correctly.

    Still seeing an error message when I try to access in UDF maintenance, but at least I have my workaround.

    ------------------------------
    Robert White
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------



  • 3.  RE: Error adding UDF To AR_InvoiceHistoryHeader sourced. Error 65 CMWUD2 line 9040

    Posted 04-02-2021 22:43
    Edited by Alnoor Cassim 04-02-2021 22:44

    Robert - I believe this is a particular Error 65 occurring since 4.x caused by the presence of a mod that overrides SO_SalesJournal_Upd in a certain way. I run into this once a year. If you do File / Run / SYZCON and type this is at the prompt and get an Error 65, the issue is present. Below command is not case sensitive.

    o=NEW("SO_SalesJournal_upd",%sys_ss) 

    If you get the 65, then without going into it, with my MD hat on, I say it's a Sage issue half the time. Definitely a "he said she said".
    Regardless workaround it like this:

    * In \mas90\Links\ rename SO_SalesJournal_upd.pvc file to something else
    * In UDF Maintenance open AR Invoice History Header entity again and click Update. Error should not occur this time.
    * In \mas90\Links\ rename back to SO_SalesJournal_upd.pvc

    Going forward issue will likely not occur again if you add another UDF that is sourced from SO Sales Journal Update.



    ------------------------------
    Alnoor Cassim

    Email: alnoor@asifocus.com
    Ph: 949-689-9887
    Orange County, CA
    ------------------------------



  • 4.  RE: Error adding UDF To AR_InvoiceHistoryHeader sourced. Error 65 CMWUD2 line 9040

    Posted 04-03-2021 18:26
    @Alnoor Cassim that was very exciting ... but alas, not the solution.

    When I ran the command in SYZCON before renaming the files in the links folder, the command finished without error.   I renamed both AR_SalesJournal_upd.pvc and SO_SalesJournal_upd.pvc for fun), and tried the UDF update.  I didn't get error 65 again, but I have a different error (error 91 program MDENH line 0120), and it does appear to point to enhancements.  The Sage KB does have this error but says ... go talk to the MDs


    Thinking a fresh start was in order, I tried to duplicate the steps after restarting the server.

    With the Links folder set with all the stuff in there, I did SYZCON and ran that command.  It finished without error.  I tried to update the UDF and received the same original error 65.  Even after renaming the file in the links folder, the error 65 still happens.

    Any other ideas?

    Thanks in advance, Robert



    ------------------------------
    Robert White
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------



  • 5.  RE: Error adding UDF To AR_InvoiceHistoryHeader sourced. Error 65 CMWUD2 line 9040

    Posted 04-03-2021 18:53
    We are also still having the same issue after following the steps.

    Do you have any custom mods or just straight up sage?

    Sent from my iPhone





  • 6.  RE: Error adding UDF To AR_InvoiceHistoryHeader sourced. Error 65 CMWUD2 line 9040

    Posted 04-03-2021 19:43

    In both client cases, there are 3rd party enhancements.   Creating the UDF on my local system and exporting that and then importing to the client system is my temporary workaround. Not perfect, but it gets the job done.  



    ------------------------------
    Robert White
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------



  • 7.  RE: Error adding UDF To AR_InvoiceHistoryHeader sourced. Error 65 CMWUD2 line 9040

    Posted 04-03-2021 20:36
    Which mods do you have? We have job Ops and Multibin as well as a bunch from DSD. If we think it is a custom mod, maybe we can get the developer to help. 

    Sent from my iPhone





  • 8.  RE: Error adding UDF To AR_InvoiceHistoryHeader sourced. Error 65 CMWUD2 line 9040

    Posted 04-03-2021 20:54
    My original client had
    - Scanforce
    - DSD Multicurrency for AP and PO only, I think
    - SWK custom programming for some little lookup thing

    The current client (where I've been doing more testing)
    - Scanforce
    - DSD custom programming
    - True Commerce (but I think it's all outside of Sage)
    - CIM Cloud

    Internally, we have DSD multicurrency, but I can't duplicate internally

    I just checked on another client with v2020 Premium and they do not have the problem.  They have
    - Scanforce
    - DSD Instadocs
    - True Commerce

    So, that's all I can tell you. I can't see any commonality as to who (what MD) to go see.  @Alnoor Cassim's suggestion of disabling enhancements makes sense, but when I do, I still get the error.

    ​​

    ------------------------------
    Robert White
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------



  • 9.  RE: Error adding UDF To AR_InvoiceHistoryHeader sourced. Error 65 CMWUD2 line 9040

    Posted 04-03-2021 21:01
    We tried that too with no luck. We have Sage working on it and actually brought DSD to help because sage is doing the whole finger pointing thing 

    Sent from my iPhone





  • 10.  RE: Error adding UDF To AR_InvoiceHistoryHeader sourced. Error 65 CMWUD2 line 9040

    Posted 04-03-2021 21:30
    Robert - I should've mentioned that after trying to rename the individual _UPD file, to then try renaming the whole Links folder, then try the UDF update. Then rename Links back regardless of result. Obviously has to be done with everyone out of the system or at least at with only the Launcher open. 

    I can dupe the error by making a certain type of change in the _UPD program. But I guess the error could occur in another class / object with the same type of change made. 

    If it still occurs then an MD type will need to step through the UDF update 





  • 11.  RE: Error adding UDF To AR_InvoiceHistoryHeader sourced. Error 65 CMWUD2 line 9040

    Posted 04-03-2021 21:46
    @Alnoor Cassim​  In one of my earlier tests, I renamed the links folder and created a new Links folder with only the default file in there.  Still had the same message (error 65 CMWUD2 line 9040).

    On a side note, I had a problem renaming the links folder back.  There was no PVWIN32 processes or the service running and I checked windows open files and nothing was opened.  In the end, I restarted the server and was able to rename the folder back

    ------------------------------
    Robert White
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------



  • 12.  RE: Error adding UDF To AR_InvoiceHistoryHeader sourced. Error 65 CMWUD2 line 9040

    Posted 04-03-2021 03:26
    We are having this same exact thing in Sage 2020 premium as well. For info sharing, we do NOT have product update 1 but we do have Job Ops and Scanco Multibin - had anyone come across with a fix for this?

    Sent from my iPhone




  • 13.  RE: Error adding UDF To AR_InvoiceHistoryHeader sourced. Error 65 CMWUD2 line 9040

    Posted 04-29-2021 12:39
    Seeing this on a Standard 2020.1 with Scanco MB as well as a Advanced 2020.1 with Scanco MB and several other third party solutions.  Only thing common is the Scanco MB.  Unable to duplicate on a stock 2020.1 system.

    ------------------------------
    David Speck II
    Tennessee Software Solutions
    ------------------------------



  • 14.  RE: Error adding UDF To AR_InvoiceHistoryHeader sourced. Error 65 CMWUD2 line 9040

    Posted 04-29-2021 12:44

    We are having the same issue on Sage 2020 (no PU1) also with Scanco MB. Note – we are on Sage Premium 2020. We have a reported case open with Sage on this (There are two or three other resellers that have mentioned having this issue). I'm assuming your error is occurring when linking to the AR_Transaction table?

     

    Tara Schinkel

    Sage 100 Consultant

    Act! Certified Consultant

    Stewart Technologies

    410 – 309 -9550 x 1104

     






  • 15.  RE: Error adding UDF To AR_InvoiceHistoryHeader sourced. Error 65 CMWUD2 line 9040

    Posted 04-29-2021 13:55
    End user first reported the error when they attempted to add a sourced UDF to AR_InvoiceHistoryHeader and once on the data sources tab, they selected either SO_SalesJournal_upd or AR_SalesJournal_upd and then the error occurs once AR_TransactionPosting is displayed in the Data Source column. 
    I was also able to duplicate the error when trying to add a sourced UDF to AR_Customer by selecting either SO_SalesJournal_upd or AR_SalesJournal_upd.
    So it seems to trigger the error whenever it attempts to read AR_TransactionPosting.
    I did observe that on my stock 2020.1 system, when you first click to edit fields for AR_Customer, i get the following message yet i have not seen this message on the client systems where the error occurs. 

    I tested another one of my 2020.1 systems that has ScanForce MB and i do not get the error and i do get this message.


    ------------------------------
    David Speck II
    Tennessee Software Solutions
    ------------------------------



  • 16.  RE: Error adding UDF To AR_InvoiceHistoryHeader sourced. Error 65 CMWUD2 line 9040

    Posted 04-29-2021 14:05

    Yeah – this is right in line with what we are seeing to. You should report to Sage. Note – someone in the group was able to replicate this in a system without Scanco installed but I think that was on Sage 2020 without PU1.

     

    Tara Schinkel

    Sage 100 Consultant

    Act! Certified Consultant

    Stewart Technologies

    410 – 309 -9550 x 1104

     






  • 17.  RE: Error adding UDF To AR_InvoiceHistoryHeader sourced. Error 65 CMWUD2 line 9040

    Posted 04-29-2021 14:27
    I'm starting to suspect this is actually related to accepting credit card, ACH, or both forms of payments.
    Can you confirm whether or not any of your installs have at least one company where "Enable Payments" option on the Payment tab in Company Maintenance is set to something other than "None"?
    In both of my installs where the error is occurring, there is at least one company with the option set to "Both Credit Cards and ACH".

    ------------------------------
    David Speck II
    Tennessee Software Solutions
    ------------------------------



  • 18.  RE: Error adding UDF To AR_InvoiceHistoryHeader sourced. Error 65 CMWUD2 line 9040

    Posted 04-29-2021 14:37
    I know for a fact mine has several companies where payments is turned on. Can you try turning it off in yours to see? It is hard to do in mine because there are 70 plus people in it all the time so if you could confirm, that would be great.



    Sent from my iPhone





  • 19.  RE: Error adding UDF To AR_InvoiceHistoryHeader sourced. Error 65 CMWUD2 line 9040

    Posted 04-29-2021 15:24
    I set the option to None and also unchecked the option to allow credit card / ACH payments in AR Options but the error persists.  I did compare date modified and size of the AR_SalesJournal_Upd and SO_SalesJournal_Upd programs across all three installs and they were identical.  I don't deal with credit card / ACH stuff much in sage 100 at all so i'm not sure if i'm missing any other settings that might need to be disabled.  Since the error occurs even with the Links folder renamed, it has to be something else somewhere but i'm still suspecting it is related to credit card / ACH payments.

    ------------------------------
    David Speck II
    Tennessee Software Solutions
    ------------------------------



  • 20.  RE: Error adding UDF To AR_InvoiceHistoryHeader sourced. Error 65 CMWUD2 line 9040

    Posted 04-29-2021 15:35
    We experienced the same (links folder was a bust). 
    Sage is looking at our data now. We sort of ruled Scanco out because of renaming the links folder.

    I am trying to remember who else in the group had this issue. I would be curious to know if they had credit card turned on. This has been a huge hassle for us so I would love to get it fixed. 

    Sent from my iPhone





  • 21.  RE: Error adding UDF To AR_InvoiceHistoryHeader sourced. Error 65 CMWUD2 line 9040

    Posted 04-29-2021 20:22

    I spoke with Dan in support a week or so ago and it's in the hands of engineering since it could be duplicated.  


    My own solution is to create the UDF and flow through on a local test system and then export from local and import to the client and it worked ok.  Not the best solution but at least I could create the required UDFs.  


    FYI, I have the issue at 2 clients.   One has APS for credit cards.  The other doesn't.   Both have DSD enhancements.  We also have DSD enhancements internally and it works on our internal system.   Can't find any pattern yet except for some third party installed.   



    ------------------------------
    Robert White
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------



  • 22.  RE: Error adding UDF To AR_InvoiceHistoryHeader sourced. Error 65 CMWUD2 line 9040

    Posted 04-29-2021 20:25
    And I actually had DSD look at this because of the enhancements and they could not see anything in regards to what is  causing it to break - FYI. Whole thing is so frustrating.

    Sent from my iPhone





  • 23.  RE: Error adding UDF To AR_InvoiceHistoryHeader sourced. Error 65 CMWUD2 line 9040

    Posted 06-22-2021 10:43
    FYI, Brian Reddeman at Sage asked me to send him the providex.dde file from both clients.  This is his feedback

    Record 000597 was missing from both files. We are not sure why but it's related to a mod. Based on the other cases it appears a developer did a dictionary merge that accidentally removed that record.

    We're adding to the client system tonight and will test it out.

    ------------------------------
    Robert White
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------



  • 24.  RE: Error adding UDF To AR_InvoiceHistoryHeader sourced. Error 65 CMWUD2 line 9040

    Posted 06-22-2021 10:46

    We are actually doing to be doing the same thing in our system in upcoming days so will keep you posted.






  • 25.  RE: Error adding UDF To AR_InvoiceHistoryHeader sourced. Error 65 CMWUD2 line 9040

    Posted 06-22-2021 10:59
    V2020 std, no enhancements, no CC processing.  Unable to create AR History header UDF.

    ------------------------------
    Jeff Schwenk
    FORMER 90M Board Member
    Bottomline Software, Inc.
    Waynesboro VA
    540-221-4444
    ------------------------------



  • 26.  RE: Error adding UDF To AR_InvoiceHistoryHeader sourced. Error 65 CMWUD2 line 9040

    Posted 06-22-2021 11:54

    Send it into Sage. And you can reference the case under Stewart Technologies or let them know about the hack for the ddf file.

     

    Note – I have shared this with Jon Reiter at DSD since Sage told me all the ones they have fixed to date had custom mods BUT based on what I heard, I did let them know that wasn't the place.






  • 27.  RE: Error adding UDF To AR_InvoiceHistoryHeader sourced. Error 65 CMWUD2 line 9040

    Posted 06-22-2021 12:03
    Thanks.

    Will gather specifics next time I am on their system

    ------------------------------
    Jeff Schwenk
    FORMER 90M Board Member
    Bottomline Software, Inc.
    Waynesboro VA
    540-221-4444
    ------------------------------



  • 28.  RE: Error adding UDF To AR_InvoiceHistoryHeader sourced. Error 65 CMWUD2 line 9040

    Posted 06-24-2021 15:13
    The 000597 record was missing from an affected system that I checked today.  I wrote the record in so it looks identical to the record seen on a known working system but the error continues to occur when trying to add the UDF.
    Were you able to confirm that whatever Sage did resolved the error in your case?

    ------------------------------
    David Speck II
    Tennessee Software Solutions
    ------------------------------



  • 29.  RE: Error adding UDF To AR_InvoiceHistoryHeader sourced. Error 65 CMWUD2 line 9040

    Posted 06-24-2021 15:16

    I am putting my file in on Friday night so I can let you know then. They told me there were 4 records they had to add but the main one was one of them.






  • 30.  RE: Error adding UDF To AR_InvoiceHistoryHeader sourced. Error 65 CMWUD2 line 9040

    Posted 06-24-2021 17:02

    The replacement file from Sage worked for the first client; we'll try the second client tonight. 

     

    I assume all that was changed was that one record

     

     

    Robert White, CPA, CA

    Munjal White Consulting Corp

    Tel – 416 703-3458 x286

    For support or general inquiry questions, please email to WebSupport@MunjalWhite.com

    Have you seen our latest newsletter?  Click here

     






  • 31.  RE: Error adding UDF To AR_InvoiceHistoryHeader sourced. Error 65 CMWUD2 line 9040

    Posted 06-24-2021 17:22
    So I assume they took your providex.dde file, corrected it, and then gave it back to you?
    I attempted to write the record into one of the systems I'm dealing with and it appeared to look identical to the record in a system that is not affected but the error continues to occur.
    I also have a case with Sage but I haven't heard from them since 5/10 so I pinged them today but no response yet.

    ------------------------------
    David Speck II
    Tennessee Software Solutions
    ------------------------------



  • 32.  RE: Error adding UDF To AR_InvoiceHistoryHeader sourced. Error 65 CMWUD2 line 9040

    Posted 06-24-2021 17:26

    That was how it was ... I gave them the file and they returned it; I didn't look at it.  One of our team added it to the client system and confirmed we could add a UDF to AR_InvoiceHistoryHeader sourced from invoicing

     

     

    Robert White, CPA, CA

    Munjal White Consulting Corp

    Tel – 416 703-3458 x286

    For support or general inquiry questions, please email to WebSupport@MunjalWhite.com

    Have you seen our latest newsletter?  Click here

     






  • 33.  RE: Error adding UDF To AR_InvoiceHistoryHeader sourced. Error 65 CMWUD2 line 9040

    Posted 07-08-2021 11:13
    My v2020.1 client is experiencing this also.  They have DSD (SO-1073 and custom programming) and StarShip Link, although renaming the Links folder still generated the error.

    ------------------------------
    Brett Zimmerman
    Net at Work
    Greater Boston Area
    ------------------------------



  • 34.  RE: Error adding UDF To AR_InvoiceHistoryHeader sourced. Error 65 CMWUD2 line 9040

    Posted 07-08-2021 12:13

    Open a ticket with Sage. They have to hack the providex.dde file to fix this. There are 4 records missing in the file related to the AR_TransactionPosting file. It's a documented issue with Sage now. You send the files in, they fix it and then they send it back.

     






  • 35.  RE: Error adding UDF To AR_InvoiceHistoryHeader sourced. Error 65 CMWUD2 line 9040

    Posted 07-12-2021 10:53
    Wow, that a super way to fix things.  Send in the file and we will fix.  How about they create a utility so we can fix it our selves AND include it in the next PU?  Do you have a KB or support ticket reference?

    ------------------------------
    Jeff Schwenk
    FORMER 90M Board Member140,000,000 is a TERRIBLE thing to waste!!!
    Bottomline Software, Inc.
    Waynesboro VA
    540-221-4444
    ------------------------------



  • 36.  RE: Error adding UDF To AR_InvoiceHistoryHeader sourced. Error 65 CMWUD2 line 9040

    Posted 12-20-2021 09:51
    Does anyone have a detailed list of the missing records in this dde file?  This is a hassle to have to send a file to Sage (in my opinion).

    ------------------------------
    Jane Scanlan
    Partner
    Next Level Manufacturing Consulting Group
    Chanhassen MN
    952-210-7758
    ------------------------------



  • 37.  RE: Error adding UDF To AR_InvoiceHistoryHeader sourced. Error 65 CMWUD2 line 9040

    Posted 12-20-2021 12:15
    I just moved my client to v2021 PU 2 and I don't think it is fixed yet.  Good topic for the MOTM webinar.

    ------------------------------
    Jeff Schwenk
    FORMER 90M Board Member -140,000,000 is a TERRIBLE thing to waste!!!
    Bottomline Software, Inc.
    Waynesboro VA
    540-221-4444
    ------------------------------



  • 38.  RE: Error adding UDF To AR_InvoiceHistoryHeader sourced. Error 65 CMWUD2 line 9040

    Posted 12-20-2021 12:21
    You have to open a ticket with sage on this and submit two files. They hack the providex.ddf file (I believe) and send it back. Jane asked me about this today for which 4 files are involved in the hack. I'm in meetings all day but I will try to look up later when I can but I do know Sage has fixed this for anyone who has opened a ticket. 

    Tara Morgan Schinkel, CPA

    Sage 100 Consultant

    Act! and Sage CRM Consultant

    Phone: 410-309-9550 x1104

    www.stewarttechnologies.com









  • 39.  RE: Error adding UDF To AR_InvoiceHistoryHeader sourced. Error 65 CMWUD2 line 9040

    Posted 12-20-2021 13:33
    Edited by David Speck II 12-21-2021 14:05
      |   view attached
    I wrote the attached utility to locate and correct the missing blank table records.  I was communicating with Elliott earlier this year regarding this issue.  He still requested the following information so they can try to pinpoint what might be the underlying cause.  He also said they would look into modifying one of the core programs so it doesn't cause this error in the future when a missing blank record is encountered.  Below is some of the communication.

    There isn't too many places that this would get changed.  Possibly Customizer when updating the dictionary? (maybe) Although, I have done a lot of tests on this.  Maybe some merge utilities or update pieces used by development partners?  I don't know yet.

    If you happen to run into this issue again on one of the files that isn't in that 2021 list.  Let me know anything that may have transpired, such as new update, 3rd party add-on, or possibly recent custom office UDF's?  So far your hunches have been pretty bang-on.  In the meantime, I'll correct what I can, and look into these areas as well.

    The utility can be called from SYZCON or executed via Windows Explorer if on a system with the Sage 100 workstation installed.  It uses the directory from the last install to update the registration of the pvxcom.exe process since it goes through the BOI.  When you run it, you should screenshot the list of tables that were found missing the header record.  If you click Yes to the prompt, it will make backups of the providex.dde and providex.ddf files and then write the missing records.  The message should look similar to this.


    ------------------------------
    David Speck II
    Tennessee Software Solutions
    ------------------------------

    Attachment(s)



  • 40.  RE: Error adding UDF To AR_InvoiceHistoryHeader sourced. Error 65 CMWUD2 line 9040

    Posted 12-20-2021 13:47
    Hi David,
    Thank you for this utility.  I downloaded it and tried to run it but cannot as I get a windows script host error:

    Windows script Host
    X
    Can't find script engine 'PvxScript for script
    'C:\Sage2021\v2021\MAS90\SOA\CheckForMissingTableRecords.pvs'.

    ------------------------------
    Jane Scanlan
    Partner
    Next Level Manufacturing Consulting Group
    Chanhassen MN
    952-210-7758
    ------------------------------



  • 41.  RE: Error adding UDF To AR_InvoiceHistoryHeader sourced. Error 65 CMWUD2 line 9040

    Posted 12-20-2021 13:56
    Edited by David Speck II 12-21-2021 14:04
    Sounds like the pvxcom.exe executable isn't registered.
    Did you try to run it on a workstation with the Sage 100 workstation installed?
    If yes, the other way to run it is to place it somewhere either under the MAS90 directory so you can call it with a relative path or place it somewhere like C:\ so you can call it without having to type a long path. Once you have it in its destination, i.e. in MAS90\CM\Script, use File > Run and then type SYZCON and click OK. At the command prompt, type CALL "..\CM\Script\CheckForMissingTableRecords.pvs".
    You can specify an absolute path too by just including the full path, like CALL "C:\CheckForMissingTableRecords.pvs".


    ------------------------------
    David Speck II
    Tennessee Software Solutions
    ------------------------------



  • 42.  RE: Error adding UDF To AR_InvoiceHistoryHeader sourced. Error 65 CMWUD2 line 9040

    Posted 12-20-2021 14:08
    David,
    I used SYZCON but used "run" instead of "call" before; now I have successfully run that utility and said yes to make the corrections.  Genius!!  Thank you so much for this!

    ------------------------------
    Jane Scanlan
    Partner
    Next Level Manufacturing Consulting Group
    Chanhassen MN
    952-210-7758
    ------------------------------



  • 43.  RE: Error adding UDF To AR_InvoiceHistoryHeader sourced. Error 65 CMWUD2 line 9040

    Posted 12-20-2021 15:34
    That is interesting ... I thought you needed to CALL providex scripts ... you can RUN them now?

    --
    Randy Marion * Software Systems Engineer *






  • 44.  RE: Error adding UDF To AR_InvoiceHistoryHeader sourced. Error 65 CMWUD2 line 9040

    Posted 12-20-2021 15:38
    Randy,
    What I was trying to say in my last response was that in my first attempt to run that utility I used the "run" command; the second attempt I used "call" and was successful.

    ------------------------------
    Jane Scanlan
    Partner
    Next Level Manufacturing Consulting Group
    Chanhassen MN
    952-210-7758
    ------------------------------



  • 45.  RE: Error adding UDF To AR_InvoiceHistoryHeader sourced. Error 65 CMWUD2 line 9040

    Posted 12-20-2021 16:26
    Thanks for clearing that up Jane .... You had me all excited for a hot minute though....

    --
    Randy Marion * Software Systems Engineer *