Sage 100

Anyone on the new SQL version reading and most importantly writing back to Sage 100 Premium? I know the old version of SQL 3.x this was not recommended because the business rules were not forced in SQL so the writing back function had to make sure they duplicated all the rules and in some cases could create issues if not done correctly. Does the new version of SQL address this issue? I did not think it did but I would like to confirm. I know I can write to it but it is more of the question of should I. Better to use SData, VI, Web Services, etc?

I don't believe the business rules are forced in SQL still.

We are writing directly to SQL for a customer, but to a very basic tables (Purchase Control) or to UDT's. We are not writing to data entry tables.

I didn't think they were but wanted to confirm. None of Sage's Material about SQL that I could find ever referenced being able to write back to SQL instead it referred to VI, Web Services, SData, etc. @KevinWesley UDT's I can see since for the most part are very basic in nature. What is the Purchase Control that you are talking about?

The Sales Order Purchase Control tables by item and product line. The customer has strict purchase controls in place by customer. So, based on entries to various UDF's in the customer masterfile, a temp table of allowed items is created and then written directly back to the tables in SQL and bypasses VI. It's a really simple table that is a ""go/no go"" type scenario. If the customer number and item are in the table, they can purchase that item. If not, the purchase control popup during sales order entry stops the order on that item.

OK thanks @KevinWesley