July 30, 2011 at 6:02 pm
[font="Tahoma"]
Has anyone used ms access as a front end interface for inserting, updating, and deleting data from a sql server database? Are there any other options available instead of .net like open source, access or others? I am trying to find the simplest way to a front end interface for sql server without using its sql server mgmt studio which I have been using tediously.
Thanks in advance. :unsure:
[/font]
July 30, 2011 at 10:31 pm
What exactly do you need to do? Access is possibly a good option but I don't really understand what you need.
July 31, 2011 at 2:51 am
The "simplest way" depends on what the requirements are and what you're familiar with.
An ACCESS solution for example might not be a good choice for a web interface.
A .NET programmer might consider ACCESS not being the best option whereas someone with a decent ACCESS experience might not prefer .NET. Others may prefer SharePoint.
July 31, 2011 at 9:17 am
Allow me to rephrase the question and exclude MS Access from it.
I am responsible for developing and editing user interfaces for several departments. These interfaces allow the end user to insert and update data which is contained in our sql 2005 and 2008 database servers. Currently these interfaces are written in classic asp. The company is going to allot me time to re-develop these interfaces in a .net environment.
I was hoping that I could be directed to one or more tutorials more specific to IIS 7 and those that give a user some guidance on developing a user interface for inserting, updating, and deleting data. Updating and deleting data will require a higher permission but that will be taken care of.
Hope this helps with better explanation.
July 31, 2011 at 9:25 am
Yes it' clearer, but if the platform is not chosen yet Access is a fast and easy tool do to that in
July 31, 2011 at 9:30 am
Try this site:
http://sqlserversamples.codeplex.com/#e2e
Provides a great deal of sample code for what I think you might be looking for.
July 31, 2011 at 11:01 am
greatsqldba (7/30/2011)
[font="Tahoma"]Has anyone used ms access as a front end interface for inserting, updating, and deleting data from a sql server database? Are there any other options available instead of .net like open source, access or others? I am trying to find the simplest way to a front end interface for sql server without using its sql server mgmt studio which I have been using tediously.
Thanks in advance. :unsure:
[/font]
Yes I have created Access Databases to perform DML and a lot of other actions when in a crunch but I prefer to use .NET. There are .NET Wizards that you can use to create simple forms if you do not need a robust application and you do not have the time to develop from scratch.
But what I think I'm hearing is that you do not find SSMS easy to insert, update and delete records?
If that is the case you don't like to write SQL statements to perform DML as a shortcut you could create a view within SQL Server and you can easily insert, update and delete records.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
July 31, 2011 at 11:58 am
Thank you for your reply. Actually I enjoy using SSMS as I write a lot of T-SQL. Where it becomes tedious for me is when I have to insert data for a declared variable that would be much easier to enter, IMO, if I were to use an html "TextArea" (I hope this makes sense).
From what I have gathered so far webforms are good for entering data into a database? At the same time I see these aspx pages where you enter the needed data and as soon as it is entered the "post back" (a guess) is displaying the data just entered with other records that have been entered in an ordered variation. This is the interface that I would like to be able to create. i hope this makes sense..
Therefore, If I can be directed to a tutorial (hopefully) that can explain how to create an interface like I have stated above it would be of tremendous help.
These are the resources that I currently have on my laptop:
MS Visual Studio 2010 Express
MS SQL Server 2008 Enterprise
MS SQL Server 2005 Express with SP4
If there are any other free or trial tools that you could recommend this would be greatly appreciated as well.
I am working mega hours trying to research and acquire the resources (applications) that I will need to develop these new user interfaces to again insert, update and delete data in sql server 2005 and 2008.
Let's forget about MS Access for now please. Another user had recommended it so I "included it".
I appreciate your help.
August 1, 2011 at 12:43 pm
allonlineaccts (7/31/2011)
Allow me to rephrase the question and exclude MS Access from it.I am responsible for developing and editing user interfaces for several departments. These interfaces allow the end user to insert and update data which is contained in our sql 2005 and 2008 database servers. Currently these interfaces are written in classic asp. The company is going to allot me time to re-develop these interfaces in a .net environment.
I was hoping that I could be directed to one or more tutorials more specific to IIS 7 and those that give a user some guidance on developing a user interface for inserting, updating, and deleting data. Updating and deleting data will require a higher permission but that will be taken care of.
Hope this helps with better explanation.
The GridView functionality in ASP.NET is obviously better than in classic ASP, and that would be a re-write worthy of the investment. However, MS Access would probably involve granting users a login account with elevated db_datareader and db_datawriter rights and also limit access to users within firewall. MS Access can connect external users to a SQL Server database via IP address, but it would invove opening up ports, etc.
If we're talking here about a need for users need to submit changes to things like meta data reference tables, then the way I handle that is to let them maintain their lists offline in Excel. When they submit changes for release, I generate a SQL insert/update/delete script from that Excel sheet they provide, and then I push that script though versioned source control and the production deployment process. Allowing users to make ad-hoc changes to data is rarely beneficial in the long run.
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply