I am planning to create a Tally Integration Series using C# and Python (already started) using TallyConnector First I want to focus on One Series which is used by most people So Created a poll
That requires So much experience and understanding of existing accounting packages , As of Now I know about Tally and I am learning Zoho, Xero ,ERP Next , Odoo After understanding existing solutions I am planning to create a open-source accounting package but it will take some Time probably after 2 or 3 years But for now I am concentrated on this Tally Integration because I recently released a stable version of TallyConnector(open-source C# library to connect with Tally)
Open Source Application in the context of ubiquity of Tally: First Milestone: Publish a schema that is compatible to Tally data. Whoever can code should use that schema for Import, Export, Report etc In that way one can benefit from other's code Sqlite database comes to my mind. Second Milestone: (Optional) Capability to handle tdl and Xml tdl Third Milestone: Server code which can store data locally as well as in cloud.
Instead of trying to create an application that is incompatible to Tally, 1. Create an eco-system that is compatible to Tally and in FOSS spirit. And if significant efforts were made... Suppose one wants to create a task that is similar /compatible to one already created by another. 1. Import from Tally and Print a pdf. 2. Use the saved data to export to Xls. Done by different developers in different programming languages. Only possible if the database is the same. 3. Another developer may combine data from multiple companies to predict demand of one particular item in the coming months. 2. By tdl, a dsl Tally is extended. So if possible we should be able use it in our application. Needed here something like parser with function pointers to execute our code. 3. Everywhere database is going remote or at least backed up remotely.
Years ago I wrote a free C like dll to post Vouchers to Tally. Not updated since then for want of time and queries. May be VB is used by most and so... It would be nice to have some place to discuss design, scope of such tool.
The dll was called from VB and VB.net sucessfully. It is not an Activex dll. so I made memory allocation and released memory through a function. This memory management makes it possible to get ledger list etc. I guess Widestring / UCS2 / UTF 16 is more appropriate as return string format. In this context tdl functions as callable dll functions (like 'CompanyName = CurrentCompany()') would also be useful third party software integration.
https://sourceforge.net/projects/vch2tally/ Last hack was to return widestring for VB developers. Earlier some simple validation like checking the existence of a Master was builtin. After GST with same name different GSTIN etc. I now think the implementation of validation should be left outside.