I'm trying to configure Crystal report to read the connection data from an ODBC, so it can read the required database given the system where it's installed.
However, the .rpt always connects to the server where it was created, ignoring the ODBC configuration (or, at least, the server name).
i've tried updating the connection and changing the ODBC, but still asks for the first server were it was connected.
is there any way to check if the connection is embed or to make the report read the whole connection from the ODBC?
This happens with most of the reports i'm working on (about 100).
I'm using Sap CR 13, and the reports were migrated from CR 8
Thanks!
open CR without a report, go to File, Log On or Off Server and it will open Data Explorer windows. Right there you can delete your old connection(right click on the connection and Delete connection) and leave the new one. Then, when you open the report, it should have the new one.
Another thing you can try is going to Database, Set Database Location... and change the old routed table for the new one.
Related
We have a set of over 10,000 Excel files that were all created from a template (don't ask). They all use the same connection string to connect to a SQL Server database. Now the name of the server is changing and there is no simple way to globally replace it in the connection strings of all 10,000+ files. Is there any way to keep the same connection string and still have the files be able to connect?
The server name is changing from "ABCNT3" to "ABCSQL16P1", so I need a way for the line "Data Source = ABCNT3" to still connect to ABCSQL16P1. Really hoping it's possible.
Disclaimer: This is a little hackish, which will make it difficult for another person to maintain this after you. However, considering your (already) bad situation, this will solve your current problem until you can determine a more-permanent solution.
If you don't already have SQL tools installed, you will need "SQL Server Configuration Manager". I installed it as part of admin tools for SQL 2017 (SSMS).
Run it from the machine with all of your Excel files.
Once it opens, pick the last one from the list, named "SQL Native Client ##.# Configuration". Expand it and choose "Aliases".
Create New.
Alias name = "ABCNT3", Server="ABCSQL16P1".
Your Excel will believe that the new server is the old server. It is pretty seamless.
I am attempting to use a Packaged Solution for my Access 2010 application that has its backend linked to SQL Server. At the moment, I'm using the .accdb file as the frontend, and I would like to distribute my application to some other Windows computers, but the Packaged Solution does not work. I had the package include Access Runtime, so their version of the frontend is running on Runtime and not full Access. However, once the application makes a request to the backend, the application does nothing, as I am not even prompted for the SQL Password as per usual with the full version. I've read on about including a .dsn file in the package can secure the SQL connection (see here), but going through steps of other tutorials to create .dsn files hasn't led to any results. Would anyone know how to correctly generate the .dsn file or if I've done something else wrong at this point?
(And yes, I understanding using Access 2010 in the year 2019 is almost a joke at this point, but I'm doing this for testing purposes. I plan to completely remake the frontend in Angular in the future.)
One other unrelated note... would it be a better idea to have the frontend hosted as a .html file like through the "Publish to Access Services" process? I did read that Access Services was discontinued last year, so would that not be possible?
Edit: This is not a duplicate of "DSN Less Connection (MS Access to SQL2016)" because A) I want to utilize a DSN Connection, not DSN-less and B) I am not using connection strings in my code to hook up with SQL.
You should be able to just create FILE dsn, link your tables, and then distribute the compiled accDE to each desktop.
However, what SQL odbc source provider did you use? If you use the SQL server ODBC provider, then that is by default installed on each computer.
However, if you linked using Native 11 (or later), then that driver is NOT installed on each workstation by default. So, I HIGH recommend you create a FILE dsn (not a user or system DSN), and link the table using that. (Access will create DSN-less links for you)
And you should NOT be seeing a logon prompt with your application. This suggests you forgot or missed the save password option.
So, I would re-link your tables, creating a new FILE DSN. And if you using the linked table manager, then make sure you check the prompt for new location to force creating of a NEW DSN. If you just re-fresh, then you DO NOT get a chance to click on the save password option during the linking process.
So, what odbc driver are you using? The native 11 or later are better, but they are not installed by default on each workstation. However, CAUTION is required here, since the older sql driver does NOT support the newer datetime2 formats. If you used these newer sql column types, they will be returned as string data types in Access and create a mess of issues.
So, first, I would re-link using a FILE dsn.
Make sure you check the save password during the re-link.
You then compile your accDB into an accDE, and then distribute that. You don’t really need to use the package wizard, since once each workstation has the runtime installed, then a simple copy of the accDE to each person’s computer will thus work fine. There is NO special connection between your accDE and the package wizard. Once the runtime is installed, then any and all mdb, accDB, and your accDE can simply be clicked on to launch + run. So for testing, you can skip the package wizard, and just copy the accDE to the target machine, click on it, and see if it works.
Edit
The prompt and check box during this process is this:
So you have to check that box to save the password. Note that you ONLY get this dialog WHEN you create a new FILE dsn.
I am creating a package for updating a table in SQL server. The details to be updated is fetching from the MySQL database. For this I am using ODBC connection manager to connect to MySQL. But this ODBC connection manager is not getting listed in the OLE DB connection manager. I can see ODBC Source and destination in Toolbox. Similarly is there any ODBC lookup for doing this?
Lookup components only support the use of OLEDB connection managers or Cache connection managers. For your purposes, you should use the latter:
Read the MySql table using ODBC
Use the cache transform to load a .caw file.
Configure the lookup to read from the cache file.
I though of answering my own question as I got an easy solution for the same. Hopefully it will become a help to other beginners in SSIS.
Creating a Datasource for MySQL is an easy task. The whole process can be done with the steps mentioned below.
Install the MySQL connector.
Create ODBC DSN.
Create datasource using the created DSN.
Lets discuss each step in detail now.
1)Install the MySQL connector.
MySql connector is readily available for download in the MySQL web site. Download the correct one for your machine and install. It will be better if you install bot the 32 bit and 64 bit versions. When I tried using the 64 bit alone, I was getting an error regarding a platform mismatch.
2)Create ODBC DSN.
Open ODBC data source administrator. If your machine is 32 bit then open 32 bit other wise 64 bit ODBC data source administrator. Mine is 64 bit machine. It can be opened by Control Panel->Administrative Tools->ODBC DataSources. Mine is 64 bit machine. So I am opening the ODBC Data Sources(64 bit)
Go to System DSN tab. Click Add button. Below window will appear.
If the connectors are installed properly as per step 1, then they should be listed here. Select the MySQL ODBC 5.3 Unicode Driver. Click Finish. The below window will appear. Enter the credentials and Press Test button. If everything is fine, it should show a success message. Then Click on Ok Button.
Then the created DSN should be listed in the System DSN tab.
Repeat the same for User DSN also. Because in the SSDT while configuring the datasource we wont be able to select the System DSN. Also when deploying we wont be able to work with the User DSN also. Creating both in same name will save the package editing time. This is what happened in my case. I spent a lot of time investigating the reason for the package failure. Finally I got this. Please correct me if I am wrong. 🙂
3)Create datasource using the created DSN.
Add a connection manager in the SSDT by right clicking the connection managers in solution explorer and selecting New Connection Manager. Select ODBC from the options available.
Click Add. In the window that appears click New. A new window will appear.
In the data source specification select the Use user or System Data Source Name. Select the created DSN from the drop down box and press Test Connection. It should show success message.
That’s it. We created the ODBC source.
Please refer my blog for the article
I have some problem with SAP Crystal Report. We have just upgraded the server, to the new server. Since the server did run in tandem with old server, we had to give it another name.
The problem, is that crystal report would not function at all to the new server. It saved the connection to old server at the rpt file, and refuses to change the connection. All properties were grayed out, and cannot be changed to new connection.
So I made a new connection, and wanted to copy the SQL query to the new connection. But when I click on View Command or Edit Command, nothing happened.
Any idea on how to transfer existing rpt to the new server?
I ended up creating dummy server with name as old server. Doesn't need to have same table or anything, just dummy SQL server. The query suddenly works, albeit errors, but I can copy them all to new report
I can create a Trace and get it up and running with SQL Server Profiler.
However, instead of going through the process of picking everything I want to trace including a particular database everytime, I just want to save the configuration, and reopen at a later time and on other computers.
I know I can save a template with the configuration in, but that is on a particular server.
Is this possible to save the configuration to a file and open on another computer?
I'm using SQL Server 2012.