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.
Hi All,
Need object reference & table name for Item Maintenance --> More --> Item Pricing Maintenance --> Customer Price Schedule --> Pricing Method --> Price Discount Amount to pull the discounted price by running the script.
I right clicked on the…
Greetings,
I'm running into a roadblock attempting to add an ODBC data source via Power BI Service via +New / Data sources page from the following URL. https://app.powerbi.com/groups/me/gateways
Here are a few facts:
The ODBC driver (for Sage…
I've connected a single table from Sage 100c 2021 to Excel (data model) via a silent ODBC connection with saved username/password. All works great for me, but if anyone else uses this excel workbook and tries to refresh the data it makes them log in a…
Probably a long shot here but whilst trying to import Sage data tables into the Power Pivot table wizard i get the following error:
'Object reference not set to an instance of an object'
Any thoughts?
User 1 created an excel file that pulls in data from Sage 100 Standard via ODBC.
Created same dsn connection (same dsn name) on User 2's computer. "Test Connection" successful with saved username/pw.
User 2 opens the same excel file and tried to refresh…
If we currently do NOT have ODBC Security within Role Maintenance enabled , what are the abilities/restrictions of users to create an ODBC data source connection?
Hello. We are having a bizarre issue with Microsoft Office 2016 and an ODBC connection to Sage 100 Advanced 2018 ERP. We use a system DSN to connect to Sage from Access to run queries and reports not available in Sage and have been doing this for years…
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…