Sage 100

Have a series of imports for a client to import customer/contact/shipto/order from a list from a trade show. If I run it on the server, it runs fine. If the customer runs it from her workstation, it tells her that ""NONTAX"" is a non-numeric tax schedule. Which is true, but who cares? Had the client change one line to AVATAX and this time it told her that ""US"" in the country field was non-numeric. So she went to the server and ran it and the Customer import finally worked perfectly as it does for me. But then she went to run the next linked import, which imports into Contacts, and it crapped out with a bunch of errors and told her Avatax had to be registered, etc, etc. There isn't even a TaxSchedule field IN the Contacts file. What on earth? I know I've had VI jobs stop working after a MS update, but that usually had to do with a Select statement comparing something to blank or 0. What would make this oozing non-numeric thing? I'm waiting to hear from the client who she logs in as on the server. But still - totally baffled.

Sounds like it's Sage 100 Advanced version. Probably a path issue. Make sure the file path to the import file is mapped the way the server would see it. Or make sure the ""On Host"" is not checked.when importing from the workstation.

If they are using Advanced / Premium and have AvaTax and you're doing a Standard / MAS90 style import(s) that involves at least an import to S/O Entry, then you have to register AvaTax on the wkstn running the import: 1) From Wkstn where import is being run copy the /mas90/AvaTax folder from server. For example copy AvaTax folder to C:\Sage on wkstn 2) From C:\Sage\AvaTax run the BAT file in there using Run as Administrator. This will register the AvaTax DLLs. I like to edit the file first and add a PAUSE command there. That way I know for sure the registration was successful.

Sorry I didn't mention that they are on 4.5 Std. And note that when I ran it on the server it ran fine but when she did, it did not.