Re: Odbc Resource Dll Is A Different
Amabella Tevebaugh
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse suscipit sapien ac sapien malesuada fringilla. Fusce venenatis, mauris id sagittis dapibus, mauris velit sollicitudin ante, a pulvinar leo orci vel erat. Nam mattis erat augue, at luctus ex dignissim et. Donec suscipit, dui at efficitur tristique, nulla nisi ornare lorem, vel dictum lectus eros nec felis.
This error occurs when installing Peer Web Service:"ODBC Driver Manager: the ODBC resource DLL (C:\WINNT\system32\odbcint.dll) is a different version than the ODBC driver manager (C:winnt\system32\odbcint.dll) You need to reinstall the ODBC components to ensure operation. Press OK to proceed. Cancel to abort." Cause Installing Peer Web Service on Windows NT Workstation 4.0 will overwrite the odbcint.dll and the odbccp32.dll files with version 2.50.30.6 of these files. This causes the version conflict message.
I'm new to MAS, recently hired on to a company using MAS 200 4.40. I'm trying to utilize some of my experience with querying SQL databases to streamline work and am stumbling over how to avoid typing in my username and password to refresh my data in Excel. Searching through the forums here has yielded some possibilities but nothing has worked. Despite making changes to the connection string I still encounter the authentication pop-up. I've set up a 'dummy' ODBC connection and tried a few different syntax sequences but haven't seen success. I'm also looking into how to trigger a login routine in VB but am not having much success on that endeavor.
I'm using Excel as my import for several reasons. One is that the MAS server doesn't seem to let me link tables between modules, which I want to do (the end goal being coordination of inventory purchases based on work orders entered into the system), and in Excel I can show the people using the data where it comes from easily. Another is that the end users are more familiar with Excel than with Access, so giving them a tool to use that doesn't require learning a new system is preferable. A third would be my skill in Access; I'm not a database guy but rather someone who has learned bits and pieces over time from exposure. So don't be surprised if you make a suggestion and I come back with 'how would I go about doing that?'
I'd also add that your Sage 100 partner (ask Sage if you don't know who it is) would be a good resource, especially since you're probably going to find yourself wanting to get off that version at some point in the near future, lest a windows update come along and stop everyone in their tracks. I find that with Sage Business Intelligence being as good as it is, I do much of my reporting in there. If you're handy with Excel, that's worth a look. I think it came out right after 4.4, so that's a post-upgrade consideration. There is lots of Sage Business Intelligence training online from beginner to advanced.
I created an alias data source (twice, at least) and have tried multiple positions of user ID/password/company identifiers in the string but none seem to work, even on my first refresh. Much of the discussion I've seen on here has been around using Access to pull data via ODBC, I'm wondering if there is anything specific to the connection string in Excel that I'm missing? Reading the article you linked to I switched to caps for the user ID, but to no avail.
I'm trying to avoid entering my credentials 3 times to access data from 3 different tables; I can't seem to organize a query between tables in different modules that will return information in a timely manner.
While I can't answer your question on eliminating the need to enter your credentials entirely, you can get it to work with only entering your credentials once. I like to use Crystal to design the SQL statement and then you can cut and paste the statement into the Excel Data Query tool and then you only have to enter your credentials once when you do a data refresh.
Business Intelligence came out with 4.5, I think. And it's much better now than then. I also like Crystal, to @Tyler's comment. One advantage of SBI is that you can use it for general reporting or financial reporting, and those a two different animals. www.sageintelligence.com/.../
Have you had success querying data from multiple modules via Crystal? I've been trying to link PO#s and SO#s to item codes in an effort to identify when low inventory parts are coming in and when they will need to go out, but any time I ask the server to provide that data set all I get is the spinning wheel. I can quickly pull those tables into Excel sheets and then merge them within the book, but then I run into the authentication hurdle I prefer not to deal with. Again, I'm just starting out with MAS and may be missing something really obvious to an experienced user.
You'll see I am using a silent DSN (I called it an alias above) and I'm only accessing the default company (and no, my password isn't actually 1234...) Is there something that I'm missing/mixing up in this? As I mentioned, I tried different locations for the UID, PWD, and Company identifiers. The string above is what the default spit out; I've tried putting the company ID next to my UID also.
ODBC exists in the folder provided, and is working per the walkthrough here: Home - Asterisk Documentation , and extconfig is configured according to The Asterisk RealTime Architecture (ARA) -VoIP-Info , swapping MySQL for ODBC and replacing names/tables with the ones in the database.
asteriskhost*CLI> module show like odbc
Module Description Use Count Status Support Level
cdr_adaptive_odbc.so Adaptive ODBC CDR backend 0 Running core
cdr_odbc.so ODBC CDR Backend 0 Running extended
cel_odbc.so ODBC CEL backend 0 Running core
func_odbc.so ODBC lookups 0 Running core
res_odbc.so ODBC resource 0 Running core
res_odbc_transaction.so ODBC transaction resource 0 Running core
6 modules loaded
Sometimes your workflow must connect to an on-premises data source and can use only connectors that provide this access through an on-premises data gateway. To set up this on-premises data gateway, you have to complete the following tasks: install the local on-premises data gateway and create an on-premises data gateway resource in Azure for the local data gateway. When you add a trigger or action to your workflow from a connector that requires the data gateway, you can select the data gateway resource to use with your connection.
In Consumption logic app workflows, you can connect to on-premises data sources using only connectors that provide access through the on-premises data gateway. In Standard logic app workflows, you can directly access on-premises resources in Azure virtual networks or use built-in service provider connectors that don't need the data gateway to access your on-premises data source. Instead, you provide information that authenticates your identity and authorizes access to your data source. However, if a built-in service provider connector isn't available for your data source, but a managed connector is available, you need to use the on-premises data gateway.
You can also create custom connectors that connect to data sources over HTTP or HTTPS by using REST or SOAP. Although a gateway itself doesn't incur extra costs, the Azure Logic Apps pricing model applies to connectors and other Azure Logic Apps operations.
You already installed an on-premises data gateway on a local computer. This data gateway installation must exist before you can create a data gateway resource that links to this installation. You can install only one data gateway per local computer.
You have the same Azure account and subscription that you used for your gateway installation. This Azure account must belong only to a single Microsoft Entra tenant or directory. You have to use the same Azure account and subscription to create your gateway resource in Azure because only the gateway administrator can create the gateway resource in Azure. Service principals currently aren't supported.
When you create a data gateway resource in Azure, you select a data gateway installation to link with your gateway resource and only that gateway resource. Each gateway resource can link to only one gateway installation. You can't select a gateway installation that's already associated with another gateway resource.
Your logic app resource and gateway resource don't have to exist in the same Azure subscription. In triggers and actions where you use the gateway resource, you can select a different Azure subscription that has a gateway resource, but only if that subscription exists in the same Microsoft Entra tenant or directory as your logic app resource. You also have to have administrator permissions on the gateway, which another administrator can set up for you. For more information, see Data Gateway: Automation using PowerShell - Part 1 and PowerShell: Data Gateway - Add-DataGatewayClusterUser.
- The gateway installation uses the same region as the gateway resource that you want to create.
- The gateway installation isn't linked to another Azure gateway resource.
- The gateway installation is linked to the same Azure account that you're using to create the gateway resource.
- Your Azure account belongs to a single Microsoft Entra tenant or directory and is the same account that you used for the gateway installation.
After you create your gateway resource and associate your Azure subscription with this resource, you can create a connection between your logic app workflow and your on-premises data source by using the gateway.
In Consumption logic app workflows, if a connector has a managed versionand a built-in version, use the managed version, which includes the gateway selection capability.In Standard logic app workflows, built-in connectors that connect to on-premises data sources don't need to use the gateway.
From the Connection Gateway list, select the gateway resource that you want to use. This list shows the available gateway resources in your selected subscription. Each gateway resource is linked to a single gateway installation.
7fc3f7cf58