Sage 100

AR_Customer_bus cannot be found Sage 100 Adv 4.4.10 - I copied working ARXXX files from my computer to the customer's computer and when i open Customer Maintenance/Inquiry I get the error that AR_Customer_bus cannot be found. Knowledgebase is no help. Using trial and error I thought I had fixed the problem by replacing the AR_Options file with a backup from the original installation. That got me in until I closed out and went back in. Replacing the Option file the second time did nothing. I have Rebuilt all the files, run the Customizer Utilities.Nothing works. Any direction would be greatly appreaciated.

AR_Customer_bus.pvc is located in the AR folder, not the data folder.

Check antivirus, it may keep 'cleaning' that file

UDFs in either version?

yes both versions and they match. So I tried to Update the data dictionary but get the message that the DD doesn't match the Original files. Tried to create a new UDF and it defaults to a Business ofject and cannot be changed.

Is it possible you have UDFs or developer fields on your AR_Customer.m4t that do not exist in the client's system? Perhaps you need to create the same UDFs for AR_Customer on client's system (or use Customizer Export on your system and Customizer Import on theirs)

Alnoor, yes that is the case. I have a whole bunch of UDFs on my system from various Customer installs in addition to our in-house UDFs. So are you suggesting that i have to add all my UDFs that have nothing to do with the Customer into their Sage 100 install? No work around?

What was the original purpose of copying their ARXXX files to your system then copying it back? Were you doing some kind of repair work on your side - Is it something you can do directly on their system?

We imported their QuickBooks data into ARXXX and all was fine. Then they told us several weeks after they had been using AR live that the database they gave us did not include QuickBook's Inactive Customers. So now we had to import QuickBooks data into MAS data where some of the missing QuickBooks data now had Cash Receipts against non-existant invoices in MAS. It was much faster on our system that to do it remotely. Strange that the first time we imported with the same UDFs, we did not have this problem.

You bring up a good point in your last sentence. The UDF problem is real in that the dictionary doesn't match the physical file but may be a red herring in terms of what the error message you first posted means. Why don't you run this from SYZCON it might give a better error. The 2nd line should give an error while the 1st one might. You can type BYE when you're done to exit the screen. oCustomer1 = NEW(""AR_Customer_bus"", %SYS_SS) oCustomer2 = NEW(""AR_Customer_ui"", %SYS_SS)