Mar 12 2021 02:44 PM
Hello team,
I need to build a database to build sql server backend and Microsoft Access as the frontend.
How to get started on it?
I built a database in the past both backend and frontend were in Microsoft Access.
Mar 12 2021 05:45 PM
SolutionWhere will you deploy the SQL Server instance you'll use? Do you already have one available?
You can download the FREE SQL Server Express and install it on your computer or a network server available to you.
Download and install SQL Server Migration Assistant for Access.
It will allow you to migrate your data from the Access accdb to the SQL Server where your database will reside.
Be sure to take plenty of time to configure the datatypes for your new SQL Server tables to be sure they are compatible and appropriate for YOUR specific database.
Also, download and install the latest ODBC driver for SQL Server. You'll need this to establish the links from Access to the new SQL Server database.
Finally, invest plenty of time reviewing some basic information about designing your Access front end to work well with SQL Server. There is a great deal to say along those lines, so I'll just point to a good starting point.
Good luck with your project.
Mar 12 2021 05:49 PM
One other consideration occurs to me re-reading your post. If you've only built one previous relational database application, then I STRONGLY, STRONGLY urge you to learn as much as you can about the process of designing properly normalized relational database applications before you tackle this project. Table design is crucial. If done right, things go well from the beginning. If not done properly, you're database will be inflexible, unreliable and hard to maintain, even more so with a SQL Server back end.
Mar 12 2021 06:17 PM
Mar 12 2021 06:21 PM
Mar 12 2021 07:10 PM
Mar 12 2021 07:13 PM
Mar 12 2021 07:15 PM
Mar 13 2021 05:44 AM
@CloudsInTheSky
That's good. You mentioned one previous Access relational database application, which could be taken to suggest limited experience. One thing I've learned from many years of participating in on-line forums like this is not to make too many assumptions. I take it that you have extensive experience with other RDBM systems like SQL Server, Postgres, Oracle or MySQL, then?
The SQL Server Express version is a free download. You can install it on your local computer or on a network. It's not intended to be an enterprise database, but for smaller applications it is quite adequate.
I know of a number of small organizations which have successfully implemented it for applications supporting more than 5 or 10 individuals. It is a great way to get started without investing hundreds of dollars in licenses for one of the other versions. Of course, if your organization already has a SQL Server available to you, you could work with the DBAs to obtain permissions for it.
Mar 13 2021 10:12 AM
Mar 13 2021 10:35 AM
Not at all complicated. I've done it numerous times with no problems. The only thing that comes to mind is that you must match the bitness of the ODBC driver you select (32 or 64) to match the bitness of your MS Office applications. That means downloading that appropriate version.
Mar 18 2021 11:52 PM
Mar 19 2021 07:41 AM
Feb 22 2024 04:57 PM
@Papo_Cardona_msn the link is not working.
Feb 23 2024 04:26 AM
Mar 12 2021 05:45 PM
SolutionWhere will you deploy the SQL Server instance you'll use? Do you already have one available?
You can download the FREE SQL Server Express and install it on your computer or a network server available to you.
Download and install SQL Server Migration Assistant for Access.
It will allow you to migrate your data from the Access accdb to the SQL Server where your database will reside.
Be sure to take plenty of time to configure the datatypes for your new SQL Server tables to be sure they are compatible and appropriate for YOUR specific database.
Also, download and install the latest ODBC driver for SQL Server. You'll need this to establish the links from Access to the new SQL Server database.
Finally, invest plenty of time reviewing some basic information about designing your Access front end to work well with SQL Server. There is a great deal to say along those lines, so I'll just point to a good starting point.
Good luck with your project.