I'm attempting to create a SSRS dataset pointing to an Access Database(I know... Access, users choice). I created the DataSource fine as below. When I create the dataset I get the following error:
Business Object cannot be created.
Any help would be appreciated.
Provider=MS Remote; Remote Server=\\MYSERVERNAME; Remote Provider=Microsoft.Jet.OLEDB.4.0; Data Source= \\MYSERVERNAME\C:\SHARE\OVERVIEWS.mdb;
Thank You
Steve
If the share exists, the correct path would be along the lines of
Data Source= \\MYSERVERNAME\SHARE$\OVERVIEWS.mdb
Related
I am able to create a connection string to query the database from an external network however am unable to create a connection via new data source and therefore a dataset in order to populate a data grid view using the external information.
I have made it so that if pc name = name of dev pc it uses local server name to connect, otherwise it uses external IP.
Is there a way to create a connection for the external connection from the dev computer as its not possible to test connection and therefore gets error that its unable to connect to specified MySQL host
When inputting data into a data grid view a connection needs to be made by assigning that grid view a source. These sources come from the datasets created from the connection string by going to project, add new data source. Because the dataset needs to be accessible externally I need to create a new connection string through add new data source. Because the dev computer and database are on the same computer I cant create the connection string using that method and therefore cant create the dataset to populate the data grid view.
Thanks in advance
You are trying to solve the wrong problem here. Just create your data source to the local database normally. The connection string will be stored in the config file. When you deploy the application, you deploy the config file as well and you simply modify the connection string in it. How do you think developers create applications for customers that use completely different databases?
i am getting two text file having same structure with different name every time.
and i need to load the file everytime to table. how can we configure our connection manager
to load data from different file name to a table. Please any one suggest.
You can use a FileName variable in your Flat File Connection Manager's ConnectionString property and dynamically set it to the different name(s) and achieve this.
Here's a detailed article that shows you step-by-step on how to accomplish this.
SSIS - Dynamically set Flat File Connection Manager
I have a server report that references a shared dataset on the server. It works fine if I add a ReportViewer to a page and set the report server URL and report path properties.
Because I need to look at the xml of the report and do some preprocessing, I:-
Manually download the report using: ReportingService2010.GetItemDefinition(path). I then convert this to an XDocument.
Do my preprocessing - this does not touch anything to do with datasets.
Load the xml definition into the report viewer using:
XDocument processedDocument;
using (var sr = new StringReader(processedDocument.ToString()))
{
viewer.ServerReport.LoadReportDefinition(sr);
}
When I attempt to view the report, I see this error in the server error logs:
Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
Shared dataset definition stream does not exist.
To get to the crux of the error, I've removed step 2 completely so that all I am doing is downloading the report, converting to xml and then loading the xml into the ReportViewer.
I do not get this problem when the datasets are embedded in the report.
Any ideas what is happening here?
ETA:
If I download the report, convert to XDocument, convert back to byte[] and then use ReportingService2010.SetItemDefinition() to save the report on the server, it displays fine in the ReportViewer (when the path is specified).
This means the problem is not in the xml<->byte[] conversions. When the ReportViewer downloads a report, using a path, it must be doing something with the referenced shared datasets that I'm not doing.
I have a workaround.
It seems to be a problem with the relative path to the shared DataSets. I presume I would have the same problem referring to shared images on the server as well.
Here's what I intend to do:
Download the report.
Perform pre-processing.
Use ReportingServices2010.CreateCatalogueItem to save a new report back on the server at exactly the same location, but using a temporary name.
Use reportViewer.ServerReport.ReportPath to reference the new temporary report.
ETA:
Actually, because the DataSet path references always start at the root, I don't think you have to store the report at exactly the same location. You can create a /Temp folder that you can easily periodically clean out.
I want to modify the connection String of a Shared Data Source on a report Server. the reason is, every week we deploy new data on the server, so I am planning to deploy new database, test it and modify the datasource so that it than connect to new database, then remove the old database.
Can anyone help me in the regards.
I tried to use this post: Updating Shared data source connection string programmatically
but I can not create ReportingService2005 object as dll is missing to which this object points.
Thanks
ReportingServices2005 is not a dll, it's a webservice
The URL is formatted as below for most 2005 instances:
https://<<Report Server Name>>/ReportServer/ReportService2005.asmx
If you add the web reference the solution you have should work
An alternative to creating a custom application to do this is to use the rs.exe utility to execute the code as a script.
Scripting with the rs Utility and the Web Service
I am in search of a tool / VBA code snippet that can port my excel data to my access table with effective columns mapping. Anybody please share if you have any idea on these.
Thanks in advance
The standard way to import or link Excel in Access is to use the TransferSpreadsheet method of the DoCmd object. The link is for 2007, but it has been available certainly since 2000, if not before. TransferSpreadsheet includes a HasFieldNames argument.
In Access 2007 you can use External Data/Import/Excel
Just follow the wizard to select the workbook, type of connection, sheet and data.
Data can be imported to a new table, appended to an existing table, or as a linked table
In Access 2003 its File/Get External Data/Import or File/Get External Data/Link tables
select file type .xls and browse to the workbook
if this task is something that u need to perform on a regular basis, you may want to consider creating a macro and scheduled task to perform this automatically. it is very easy to settup and I can outline procedure if need be