I have to create a web form and store all kinds of data from the page, the data will be text, num, email and checkboxes.
I have to store them in a database SQL. I have to deploy the same page in the sharepoint server and users will be able to use that page to fillin the details once the details are filled in it should be loaded in to the SQL seperate databse.
could anybody tell me what would be the best approach.
Please give me rough idea so that I will take the steps to get it complete.
Do you have to use a SQL database? You could simply use SharePoint lists for this type of functionality.
If you HAVE to use SQL then look at Business Connectivity Services through SharePoint Designer 2010, or if you are using WSS 3.0 or MOSS 2007 then look at creating custom web parts.
Related
I'm starting a new project where we are expecting to migrate desktop based Access 2016 applications (with a lot of backend VBA and relationships between the tables) into SharePoint 2016 on-premise and very soon, SharePoint Online. From what I've been told, we'll be given site permission to a SharePoint site that we can do whatever we want with. I am hoping that with SharePoint 2016 on-premise and eventually SharePoint online means that there is a SQL Server and eventually Azure SQL Database that I can migrate the Access backend tables and queries, as I know SharePoint lists will be inadequate for this, despite the false notion that SharePoint lists are an equivalent substitute for database tables.
My concern is how to build the custom forms, perform the needed business logic, perform CRUD operations, and upload data in the form of Excel files from the SharePoint site to the backend.
I'm new to SharePoint and given that it does not support VBA, that Microsoft cut out Access Web Apps earlier this year, and they are phasing out SharePoint Designer 2013 and InfoPath, some research over the past week indicates my best options are building custom web application using ASP.NET Core and somehow deploying that to the SharePoint site and subsites that we have control over, or developing a lot of HTML, CSS, and JS to create the front-end interface. I had read about the Business Connectivity Service to get and post data to / from the SharePoint site front end and the DB backend, as well as using Javascript and AJAX calls to do CRUD operations between the database and the frontend. I looked into PowerApps and those seem insufficient, and I'm still trying to distinguish between SharePoint web parts and SharePoint add-ins.
Is any of the above even a feasible option? Could someone chime in on a better path to go about this? What technologies would I need to best go about this?
Support for moving tables from Access to SharePoint remains a choice and option.
So all of your VBA code etc. will work as before. The only real question is if you want to move your data to SharePoint tables in place of using SQL server.
SQL server tables are far faster than SharePoint tables.
However, you can certainly consider moving your tables to SharePoint. When you move your tables to SharePoint (or SQL server), then Access code, forms, reports etc. and EVEN your VBA code will work as before. What this means is that you continue to deploy the Access application to each desktop. The only difference is now your tables are on SharePoint, or SQL server.
The above choice does not result in a web based application.
So you can move the data, but your application will remain a desktop application.
If you looking to build a web based application, then Access is the wrong tool – you need to adopt something like Visual Studio.
So you can continue to use Access, and put the data tables into the cloud, or on-site SharePoint - but the application will be still desktop based.
I have used the following extensively over the last couple of years and I am happy with the experience:
Azure SQL Database as a back-end
Flow for automation and as an interface to the DB
PowerApps for forms, desktop apps and mobile apps
Excel for reporting (Get & Transform aka PowerQuery and DAX), especially for printing reports
Power BI for dashboards (limited use)
Yes, PowerApps has drawbacks, but there are a lot of realistic workarounds out there and new features/improvements are being added regularly.
I have also used SharePoint lists as data sources, but almost always then migrated to Azure SQL Database.
i am a Sharepoint administrator of a small farm. One of our solution provider has created a huge amount of WebSites at an SharePoint 2010 that have a hierachialy order. And every WebSite has a Custom list with the name "User. Now i want to extract from every WebSite this list into one csv file. The best would be to also extract the Name of the WebSite directly as a new column.
I understand that i have to use the SPSiteDataQuery Class but i am new to developing for sharepoint so i am not sure where to start. Also i would like to have it to run weekly, like some kind of service.
I should note that i have some knowledge in c#
Can someone help me please ?
MG,
Using SharePoint Timer Job you can execute you code weekly base then fetch User data from all webs.
I am using WSS 3.0 and trying to restore a mdf. I attached the database in SQL Management Studio, created a new web application, and associated the database to it. When I go into Central Administration-> Application Management -> Content Databases I see the WSS_Content and it says Sites: 2. One of the sites looks more similar to the other. I was able to log into the Sharepoint web app that has the db attached to it, and while it gives me the basic structure of the backed up site, the content of lists is blank, that was the data I was really after (Announcements, tasks, etc exist as lists but are empty). How do I get access to this?
Kindly remove your old database and make newly added database as a default/only database for your webapplication
I'd link to the the data from SQL Server into an Access database.. and then use MS Access to write these values back into sharepoint.
I've written a LOT of data to sharepoint using MS Access.. and I love the functionality.
the data is in SQL server.. but it's got different guids, or it's not wired up from what I'd assume.
You have the data posted to the SQL Server instance.. I'd just link to it in MS Access, write a couple of queries.. recreate a couple of lists.. and then push it from queries based on Access linked tables (to sql server).. and then jam it into Access linked tables (to sharepoint).
Open Access. right-click link basically. times two. and write a couple of queries.
If it was me, and it was just a couple of lists, I'd do this in a couple of minutes I swear.
i want to display the SQL server data which is in table form into the SHarepoint.
I dont have sharepoint 2007/2010
I just have SHarepoint services 3.0 and sharepoint designer 2007
please help.
I think business data catalog cant be used in this version.
IS it true ?
do i have to go for paid version ?
You could use SharePoint designer to create a webpart that shows sql data. Look at the following article. YOu cannot use that data in another way (i.e. as a column in a list or something linke that, you need the BDC for that).
I support Rational clearquest for my company and have been asked to show some of the data in Sharepoint.
I can query the data in Clearquest no problem (Using Toad) but have no idea about how to go displaying it in Sharepoint.
The data I'm querying contains dates and ideally I'd like to be able display it in a sharepoint calendar but list format would do for the moment.
Can anybody offer advice on even where to start?
Thanks,
Joe
Whilst you could do the bare bones approach suggested by Ben there are lots of options that will give you a 'leg up' especially if you are just displaying data.
Your first look should be at SharePoints Data View Web Part (DVWP). There is a length walkthrough here and some great tutorials by Laura Rogers
Very similar but if you hate SharePoint designer there is Lighting Tools Data Viewer Web Part
If you are using MOSS you could use the Business Data Catalog (BDC) - Display business data on a SharePoint site
There are other 3rd party options too that don't require MOSS such as Layer2's Business Data List Connector (BDLC)
If you have technical resource you could (expanding on approach suggested by Ben) write your own Reusable SQL Data Viewer Web Part
You would have to develop a sharepoint "feature" such as a webpart. You could then display retrieve the data from the db and display it however you want. You would basically be developing a asp.net component/application but with certain restrictions that sharepoint forces on you. You can read the basic steps here