Sage 50 can import CSV files, but it sounds like you want something more robust than that. There's a separate forum for the Sage 50 SDK. I would suggest posting your question there https://sagecity.na.sage.com/support_communities/sage50_accounting_us/f/sage-50-u-s-software-development-kit-sdk

You should also check out the 3rd party tools available at https://www.multiwaresoftware.com/.

Sage 50 can import CSV files, but it sounds like you want something more robust than that. There's a separate forum for the Sage 50 SDK. I would suggest posting your question there https://sagecity.na.sage.com/support_communities/sage50_accounting_us/f/sage-50-u-s-software-development-kit-sdk

You should also check out the 3rd party tools available at https://www.multiwaresoftware.com/.

Yes.  I want to either develop and/or find a real interface.  Thanks a lot for your prompt reply.

Where and how could I get in touch with someone who could explain how to interface with Saga 50 DB?

I understand the application is based on Pervasive PSQL.  There is plenty of information on the web regarding this database and it seems that its tables can be updated via SQL query.  The issue now would be knowing the table structures, which I figure are not publicly available, or using an API. 

Also, reading through you website, I read there is something called "job ID".  I would like to understand what that is and how it is used.  It sounds like something I have been looking for in Quickbooks but did not find, which would relate an order (customer order).

I posted my previous question in the community you recommended but I have not seen a reply. 

Interfacing with the data is outside of my skill set. I would suggest talking to someone at MultiWare or DataSoft

In Quickbooks, jobs are really sub-customers. But in Sage 50 a job is a separate entity. As such it has it's own ID, just like customers, vendors, and inventory items do.

If you have a copy of Sage 50 you can get details of the files by going to the Help menu > Help Topics, then on the Index tab search for "data (.DAT) files".

I wouldn't recommend accessing the Sage 50 database directly, except as a last resort.

The reason is that the database is subject to change from release to release, and those changes may break your code. Further, the information stored in the database is nuanced and difficult to understand, so it may be hard for your code to interpret this information correctly.

I suggest you use either the .NET API or the COM API, if you can, rather than accessing the database.