User interface

  • I am new to SQL server and currently using Access 2007. I am just wondering could someone attach a screen shot of what the user interface looks like for SQL server 2008?

  • Use this link to get a small (very small) image of SSMS

    http://en.wikipedia.org/wiki/SQL_Server_Management_Studio

    If everything seems to be going well, you have obviously overlooked something.

    Ron

    Please help us, help you -before posting a question please read[/url]
    Before posting a performance problem please read[/url]

  • So this is what the user sees on the front end? This is the actual window they would be working in to retrieve information and so forth? It is very different than the forms and reports you create in Access.

  • and a bevy of images here:

    SSMS 2008 Images/Screenshots

    Lowell


    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

  • todd.ayers (4/8/2013)


    So this is what the user sees on the front end? This is the actual window they would be working in to retrieve information and so forth? It is very different than the forms and reports you create in Access.

    It is a powerful tool, what a user can do depends upon the user's role and permissions.

    Before you switch to using SQL server I suggest that you download and become acquainted with the strengths and weakness of allowing users direct access to database information (displaying / adding new data/modifying existing data, etc., etc.)

    There is a free version of SQL Server known as SQL Server Express available at

    http://www.microsoft.com/en-us/download/details.aspx?id=29062

    you can import existing ACCESS tables, queries, etc. into the express version, and experiment with same. If in so doing you have any additional questions post them and many others will be willing to assist your.

    If everything seems to be going well, you have obviously overlooked something.

    Ron

    Please help us, help you -before posting a question please read[/url]
    Before posting a performance problem please read[/url]

  • i would call SSMS a developer tool, and don't think it's really a tool for end users to be working with; it doesn't have any place like Access does to build forms or reports..

    Lowell


    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

  • Thank you so so much for all the help you guys have provided. My boss is the one wanting to go to SQL server but doesn't know anything about it....and I am not too update on it as of yet. I don't think he realizes there is not really a front end/back end like there is for Access.

  • I have seen Access Forms running over the top of SQL server, it works but its far from ideal.

    Is the intention to port the Access application directly to SQL server? If it is then I would suggest you write an application to sit over the top and act as the User interface.

    _________________________________________________________________________
    SSC Guide to Posting and Best Practices

  • http://www.access-programmers.co.uk/forums/showthread.php?t=216956

    ________________________________________________________________
    you can lead a user to data....but you cannot make them think
    and remember....every day is a school day

  • It's still hard to beat Access as rapid application development environment for building data entry forms. If your access tables are properly normalized and have proper keys you can import the tables into SQL Server, create linked tables in access and then bind your forms to the linked tables with a minimum of effort.

    It's a reasonably low cost solution for small to medium amounts of data/users. This setup can get a bad reputation because often poorly designed access databases get 'upsized' to SQL server.

    I would evaluate your design before moving to SQL Server. If possible import your tables into SQL Server, generate DDL and start a new thread here asking for an evaluation of your database design.

Viewing 10 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic. Login to reply