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.
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 am encountering an intermittent "[ProvideX][ODBC Driver]Internal error" within an Excel workbook containing several worksheets, each of which contains a Microsoft Query (MSQuery) to various Sage 100 Advanced v. 2019 PU 2 files/tables. The query results…
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…
We have a customer that uses view tables created to optimize queries run in MS Query. These queries run in 32-bit ODBC and 32-bit Excel, but do not run with the 64-bit versions of the same. All other tables aside from view tables are able to be accessed…
Hi all; I've been having some serious difficulty finding an answer to this issue, which has led me to create my first post here.
I have an access database that pulls tables from all companies by use of pass through queries. Connection strings are handled…
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…
