Chris Burke

Yeah, I can see the appeal of doing it your way. I wonder if there's a way to fool the AddIn synchroniser so it *thinks* the file should be there and doesn't try to delete it. Need to do some jiggery-pokery with the SDBX manifest. If I find myself at a loose end I'll try it!

I've never tried building into AssemblyCache - I've always built my debug assemblies directly into the Sage 200 client folder (you have to be careful about which dependencies you allow it to copy over) and never had any problems (except when I've ignored my own advice and *haven't* been careful about which dependencies I let it copy over).

Usually something like this is caused by the Sage 200 Secured Services service having a problem (application pool stopped?), but you typically get a more descriptive error message if that's the case. How about clicking on the blue 'View details' link and telling us what that says?

The KB article is correct. However : if you go back and look at the article again, you'll see that up at the top of the screen it says "United Kingdom" - indeed, there's even a little Union Jack showing next to it. The 'about' screen in your screenshot, however, says "U.S. Edition". The KB article isn't referring to the same piece of software that your accountant is running. The software sold as "Sage 50" in the U.S. is entirely separate and distinct from the software sold as "Sage 50" in the UK, so the information in the article is not going to be relevant. I'd like to be able to offer some further advice, but I've never seen the U.S. software (I'm in the UK), so I'm entirely ignorant as to how one might go about importing data into it. You might like to raise the question in the appropriate section of Sage's Community Hub : https://communityhub.sage.com/us/sage50_us/

Right here : https://my.sage.co.uk/uk/communities/developers/developer-centres.aspx

Right here : https://my.sage.co.uk/Sage200SDKDocs/html/DOC0057_Overview.html