Welcome to the Sage 100 Support Group on Community Hub! Available 24/7, the Forums are a great place to ask and answer product questions, as well as share tips and tricks with Sage peers, partners, and pros.
Just a PSA- Had a customer who users MS Query extensively reach out today to tell me that it seemed that the MS Query function seemed to have been removed. Fortunately it's racy to add it back.
Open Excel, select "File" from the toolbar, then "Options…
This is happening with a single table MS Query in Excel 64-Bit when accessing large individual I/M and P/R files and continues after rebuilding them (Ex. IM_ItemTransactionHistory) . I reviewed the other thread on this error, but nothing applies other…
I have been attempting to simply change the data type of a column for a query I am running through the ProvideX ODBC but I keep getting errors, and I am wondering if this scalar function is not available here. Simply, I am trying to query the IM_PeriodPostingHistory…
I have an excel spreadsheet that uses the SOTAMAS90 ODBC 64 Bit System DSN to update some data from our AP tables.
When I open this spreadsheet on the server with Sage 100 advanced installed the query completes and data is updated is less than 5 seconds…
We are querying invoice data to read from MAS using the ProvideX ODBC driver from within a custom application. Within the custom application, we have tried specifying credentials explicitly within the connection string used to open the ODBC connection…
I am writing out a program and I keep getting this error on my sql statement
Error: Expected lexical element not found: <identifier> (State:37000, Native Code: 3F7)
Here below is my sql statement. I am nesting a select statement.
SELECT ItemCode…
MAS 90 version = 4.30.0.23 ProvideX driver version = 4.21.1000 I am attempting to query MAS 90 data using the ProvideX ODCB driver. My queries are running, but no data is returned.
1) MAS 90 has been set up with a role that gives me read access to all…
We use SSIS to grab all the information from MAS for use in reporting. We use the ODBC driver to do this.
This works with no issues the majority of the time. Occasionally, but still often enough, there will be an issue with the extraction, causing…