I need to export excel file/sheet data from Sharepoint(file is on Sharepoint site) and import to SQL using SSIS. Is this is even possible. What are the steps.
I know i can download these excel files from SharePoint site to a folder and then import to SQL, that's easy! but i need to know how to do it directly from Sharepoint site.
Thanks!!
If you file is stored in SharePoint library, you can access it as if it were on a network location.
Open SharePoint Library with your Excel file in IE browser.
Go to Library Tools -> Library tab.
In Connect & Export section there should be Open with Explorer button.
Click on it and you should get a Windows Explorer window. Copy the path from this window's header to SSIS Excel connection manager and you should be able to access your file directly from SSIS.
If the button is grayed out that means you are lacking access privileges. Talk to your SharePoint administrator.
Related
I have an old Access 2000 32-bit application that contains forms and code that I'm attempting to convert to an Access 365 64-bit app. The old db is password protected but I have the original System.mdw file that was used to create it. I can open it on my still running Windows XP PC with Access 2007 just fine. I can see forms design and the VBA code. I can save it as a ACCDB file but I can't open that on either a Win 10 or 11 PC using Office 365 or Access 2010.
A lot of valuable design and logic went into this old app that I don't want to lose. Any help would be greatly appreciated!
First up, if the database needs the mdw security file to open, that database is NOT password protected, but is secured with what we call Access security, or better said what we called Access workgroup security (or it been so long, perhaps user level security). That's not password protection, that user level security.
This security can only be used with a mdb file - does no work with accDB file. However, to change into a non secured file, you have to be attached to the mdw file.
So, assuming that you are able to open the secured database with Access 2007?
Then what one needs to do is REMOVE the user security that exists on the database.
The most easy way?
Open the mdb file (along with the mdw file) in access 2007. No doubt you are either using a shortcut that specifies the mdw file, or you are going to the security setup and choosing that file.
So, how to "remove" the security?
Well, you have the mdb file open in 2007. So, now close the database but DO NOT exit a2007. (the reason is you are STILL attached to the mdw file).
Now, create a blank new accDB file (and you still attached to the mdw file).
Now, import all of the forms, and "everything" into that new accDB file.
You can now exit a2007, and re-launch (without using that mdw file). Or you can move the accDB file to your newer computers - a2010, or even 2019, or the new 365 version should then be able to open the accDB.
You can also launch a2007, create a new accDB. Then as noted, exit, and now re-launch a2007 with that correct mdw file to allow open/use of the mdb file.
At that point, you close the mdb file (but not exit access), open the new accdb file, and once again simple import all forms, code etc. into that new accDB file.
So, either way, you simple need in a2007 need to be attached to the mdw file, and that will THEN allow you to open the accDB file, and import everything from the mdb - do this will de-secure the mdb file, and you wind up with a new accDB file with everything having been imported.
Once done, then that accDB file can (should) then work and able to be used with any recent version of access.
Now it is "possible" that you can also try a save-as in a2007 and create a accDB file, but my memory seems to suggest that you have/had to create and then import everything.
however, if you are able to save as accDB, then that file should work in newer versions. If it does not, then try the above suggested import idea.
I should also point out that the file format for x32, and x64 ARE the same.
In most cases, the VBA code should run and work (do a debug->compile in the VBA editor to see if any code will not compile). Even that VBA code for the most part in x64 bit versions of office/access 365 should work fine.
However, if that older program uses what we call windows API code, then such code can be fixed - but will require some efforts on your part.
Also, while not all that common in Access, if they used any ActiveX controls, then those have to be changed for x64 bits. But, one step at a time, you want to get a accDB that you can open - from then you can check/see and test if any VBA code requires changes (it should not).
I have a database that is stored on my local machine. I would like users on my network to access that database through power bi. Can someone point me in the right direction?
Well do you use the access file now with power BI? In ALL and in EVERY case WHEN you use a access data file, you are using a full + standard + legal path name to the access file.
So, if you want users to be able to open the Access accdb file, then the accdb file has to be placed in a folder that is open for use by anyone on the network. So, if you are using power BI with Access now you note that there is a FULL + legal path name to the Access file from that power BI system.
So, if you want to pull data from Access into Excel, then the Excel user needs to be able to see the accDB file in some folder and have rights to that folder.
So, if you want to pull data from Access into Word, then the Excel user needs to be able to see the accDB file in some folder and have rights to that folder.
So, if you want to pull data from Access into "your whatever application" that is NOW connecting to Access", then the whatever application and the users all need rights to the folder where the Access accDB file resides.
I have created quite a large Access 2016 db. It is now ready to share with the business and needs to be put onto SharePoint. I've tried just uploading the file to a SharePoint document library, however users cannot edit the database (there is a lot of VBA code that runs SQL commands that write data input by users into the database).
Is there a way to share the database that allows users to open it from SharePoint and let the VBA write to the database/tables?
That is not possible as SharePoint isn't an SMB fileshare, neither is OneDrive, DropBox, etc.
The SMB fileshare is offered by a Windows Server or a Linux box with Samba installed.
I've been asked to develop a report using Jaspersoft studio to generate the report template and then use jaspersoft server to have users that generate the report on demand, using data from a CSV file, instead of a DB.
I've been able to generate a report locally using studio, upload the report to the server, but I'm not able to generate the report from there.
I've been looking around and every solution that is proposed is to inject the data into a DB and then generate the report using that. But in other post in the jaspersoft community, it's said that CSV support is going to be added by early 2014, so I guess it's already there.
So, What I think that might fix it is:
1) Add the CSV file to the server, but how to link the report (.jrxml) and the dataAdapter (.xml)?
Right now, I've uploaded it to /contentFiles/xls/energy.csv, but if I put that on the data adaptor, jaspersoft can't find it:
I assume because there is no ip to the server, so it might think it's a local file. If I use the ip to the server, in my case, http://...***:8080/jasperserver/ (* for security reasons) and add after that /contentfiles/xls/energy.csv it still can find it. So, how to link the adaptor to the csv file on the server?
Also, since this csv file will be generated from time to time:
2) There is a folder where I can place or generate the csv file to be updated on the jaspersoft server?
There are a couple of steps to follow in order to have a file-based dataAdapter correctly deployed in JasperReports Server. The following steps were performed with Jaspersoft Studio 6.4.0 and JasperReports Server Pro 6.4.0.
Assuming you have your CSV file in your workspace
(I'm using the CsvDataSouce.txt from the csvdatasource sample)
you begin by creating the data adapter from the Repository Explorer view by pointing to your file and setting up the column names.
You then export your newly created adapter to file by right-clicking it and choosing the Export To File option
(I'm saving it along the CSV file)
At this point you could even delete the adapter from the Repository Explorer view and keep only the saved file to avoid any mistakes. You then create your report by picking the workspace dataAdapter and continue with your report design.
Publishing the report to the server at this stage would not push the dataAdapter files. You need to specify the report's Default Data Adapter property from the properties panel
by picking your workspace adapter
You can now publish the report to your server and the wizard will automatically discover the additional resources to be published
Make sure you pick the Don't use any Data Source option in the last dialog
Your report is now linked to the one from the server with this set of properties:
<property name="ireport.jasperserver.url" value="http://localhost:8080/jasperserver/"/>
<property name="ireport.jasperserver.user" value="jasperadmin"/>
<property name="ireport.jasperserver.report.resource" value="/public/CsvReport_files/main_jrxml"/>
<property name="ireport.jasperserver.reportUnit" value="/public/CsvReport"/>
You can continue to work on it and Jaspersoft Studio will prompt you to republish on each save.
Your CSV file is now a JasperReports Server repository resource that you can update whenever you want, either through Studio or Server's UI. If you don't want it to reside on the JasperReports Server side you could simply use an external URL pointing to your file when creating/editing the dataAdapter file.
i tried to copy the file using copy/xcopy from batch file, but it is not working.
then i downloaded ssis integration tool kit from (http://www.kingswaysoft.com/products/ssis-integration-toolkit-for-microsoft-sharepoint/download ) and tried to create a sharepoint connection manger to send the file using file system task, but getting error as unknown namespace type for user in sharepoint connection manager while creating connection manager.
is there any other way to send the files to sharepoint.
Thank you for downloading our software.
It looks like you were not able to build the connection with SharePoint. Can you post the full error message so that we can better assist you?
Once you have created the SharePoint connection manager, it would be fairly easy to upload files to SharePoint using the Premium File Transfer Task which comes with our SharePoint Toolkit.
You can also reach out to us through our official support channel if you have any further questions.
Best regards,
KingswaySoft Support