Sage 100

Not so urgent help needed but need to get an issue solved. The client configured a VI Job using ODBC to an Oracle database some time ago. We can still run the VI job but it runs all night if you try to click the Table button in VI. Now that we moved to a later ODBC on 4.5 of MAS instead of 4.3 of MAS it gives an Error 15. There is an old article on the Sage Knowledgebase that says this just will not work. It did work. It doesn't work now. The ODBC for the Oracle database does with through Crystal. Any help is appreciated @Sage100UrgentSupportNeeded

What specifically does the KB say doesn't work? Custom SQL in the Table button is common. You might try a pass through query and pull the data through from Oracle through MS Access.

I've had error 15s on ODBC VI jobs before and making a new VI job by copying from the old one seems to work.

It turns out the client made some changes to the oracle database. I am not sure what he changed but basically presented a smaller database to Sage. Apparently the Tables button in VI wants to load the entire database. We also had to change the SOTA.ini to present 10 records. Then we could edit/create the SQL in the Tables screen of VI.