This question already has an answer here:
Closed 12 years ago.
Possible Duplicate:
Edit SQL Extended Properties in SharePoint 2010
Hi everyone,
I know how to view/edit table data from an external SQL (non SharePoint) database from my SharePoint 2010 web front end.
However, I also want to view/edit the extended properties (metadata) as well.
How can I do this?
Thanks!
You don't make clear if you are wanting to access a SharePoint Database (not supported as NLV say) or a.n.other database via SharePoint.
I am assuming the latter.
There are lots of table viewer/editor web parts but I don't know of any that let you work with metadata so you're probably going to have to develop your own - this guide and this one are for a viewer but should give you a head start.
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.
This question already has an answer here:
Is it possible to connect to an embedded DB with Raven Management Studio
(1 answer)
Closed 5 years ago.
RavenDB server comes with a web UI Studio letting to look what's inside. But what's the way to take a look in an embedded RavenDB?
If you are running a test you can use the WaitForUserToContinueTheTest method. Otherwise I guess you'll need to start the http server yourself.
We have an SQL Express database with an Access 2003 front end which we can convert to Access 2010 or 2013. The database has a lot of forms, queries & tables & complex VBA code.
What is the procedure to make this web enabled so a limited number of our customers can logon and update information in the forms
Will it require VBA coding from scratch, some minor changes or I don't need to change the VBA code at all?
Please note that I am talking about access web based database which
can be hosted on SharePoint site. I am not talking about php, java or
.net bases full fledge web application. So i think a person having
expertise in MS Access can answer this question.
Thanks in advance!
This question already has answers here:
Where are My.Settings saved in VB 2010 .NET?
(4 answers)
Closed 8 years ago.
I am creating a VB.net application and including my database credentials in the settings of the project, so to access i use:
My.Settings.SettingName
Is there any way a user using the application can view these settings?
I am worried about someone being able to log into the database if they ever manage to see the settings?
Application users can not see these settings. The only way to see the settings is to look at the code as a developer.
EDIT:
In my humble experience, the best choice for hiding a connection string in your app, considering the environment I work in, is to hide it in the vb code. You can make a database utilities class, and put your methods and properties there - methods being connect, execute commands etc, and a private property which is your connection string that other methods in the class use.
Other people can see the connection string, like other developers, or people who are browsing around the same files you have access to, but upon deployment, it will be very difficult for someone to extract the connection string out of yourapp.exe.
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.