Call Sage: 877-495-9904

Sage 50 Software Development Kit (SDK)

turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Reply
Topic Options
swheeler Bronze Contributor
Bronze Contributor
swheeler
Posts: 266
Registered: 06-22-2008
0

Re: 2012 SDK API requirements vs previously designed code

[ Edited ]
Options

01-31-2012 08:49 AM - last edited on 01-31-2012 09:49 AM

Yes, it's a completly different approach to integration. Make sure that all of the functionality that you require is supported by the new API before you jump-in with both feet. It's new, and the development team is adding-in new functionality with each release of the product.

 

Just a quick edit on this reply. You can still use the COM-based integration with version 2012, it's still available; you just need to compile against the new DLL.

Scott Wheeler, Owner, Noverhead Software
Adv. Mfg for Peachtree: MRP, Inventory Lot Numbering w/ Traceability, and Price/Volume Disc. by Vendor
http://www.noverhead.com
Message 1 of 2 (170 Views)
 
Reply
tsfllc
New Member
tsfllc
Posts: 1
Registered: 01-30-2012
0

2012 SDK API requirements vs previously designed code

Options

01-30-2012 03:22 PM

I have ONE customer using Peachtree Accounting 2012.  They just upgraded from Complete 2010.  No customers on 2011.


After finding this out the hard way, I have downloaded the new SDK.  Received my Sage App ID for my VB.NET application .  Now have the code modified to requestaccess/verifyaccess/open a company.  Working.... and then I realize ALL of my existing code is developed for use with Interop.PeachwServer.

Do I have to rewrite my Peachtree integration code to acommodate the API required for a newer version of Peachtree?

 

Message 2 of 2 (173 Views)
 
Reply