Nigel Bogle

This reply is for Colin. I had this little issue earlier this year and for me it was caused by not setting the company number when I connected to the application. This scenario was explained in the SDK under the heading 'Connecting to Sage'. I hope this helps.

This is a request for ADVICE please. I am attempting to build an Integration interface between Sage 200 Professional On Premise 2023 R.1 and a C# Solution containing more than 50 projects developed in .Net 4.5 and .Net 4.6.1. For a long and complicated reason which I can't really go in to here, we just cannot upgrade these existing projects to .Net 4.7.2 which is the current .Net version for Sage 200 2023 R1 dlls. We obviously can't use .Net 4.7.2 dlls in a .Net 4.5 / 4.6.1 solution because it just won't compile. We are asking if you have any suggestions please? We are considering using older Sage dll versions that were created under .Net 4.5 or lower or maybe 4.6.1. We are asking if you could inform us if there are any such dlls available, where we could get them from and most importantly if they would work against an existing implementation of Sage 200 2023 R1 and if there would be any adverse results in doing this. Thank you in anticipation.