First and foremost you should take the BOI and Data Files classes at SageU (Sage University, where they teach you about the program) to fully understand the file structure and how to write scripts correctly.   When you take the BOI class you get documentation.

If you are simply looking to do batch inputs, take a look at the Visual Integrator module, which allows importing data into Sage tables without having to learn BOI.

There isn't much you can't do using BOI and extended ProvideX coding using CALL/PERFORM.

MD Lite.

Maybe if you told us what data you plan on reading and writing to Sage 100 we could help determine the best way

My vote is Sage do a better job of defining their object model (framework) to COM/OLE standards.

Requesting definition info at the COM level is almost nonexistent.

I want to read & write from below data:

1. Customer list

2. Purchase Order

3. Quote details

4. Warehouse code

Request you to let me know the best possible way to write back to these data.

1. You can create new customers with code.

2. Yes you can create purchase orders with code

3. Yes you can create new quotes with code

4. Yes you can create new warehouses with code but probably easier to just do it manually.

You can read from all the tables involved with code or with ODBC.

VI imports would work too, for batch uploads.

BOI is powerful but has a high learning curve, while ODBC plus VI could be working in a matter of minutes.

Note that with ODBC you can only READ data, you cannot Write back to Sage 100 using the SOTAMAS90 DSN

If you truly understand how data is written to ProvideX files, a PVXPlus R/W driver might be the cheapest and fastest way to simple 100 updating. Keep in mind it might void your support with Sage if they discover it's use.

Sage let DSD use a custom version of ProvideX from MK for their now discontinued SQL Mirroring offering.

I think the R/W ODBC option should be a use at your own risk and Sage unsupported.