Overview

Lesson 1: SQL Server: Connect, Pros, Cons

S M L XL FS | Slo Reg Fast 2x | Bookmark

In Lesson 1, we will provide an overview of why you might want to connect your Access database to an online SQL Server, discussing the main benefits and drawbacks, the differences in security and accessibility, and the tools and services you will need to get started. We will talk about issues such as speed, safety, reliability, management, and what your users will need to connect. We will also discuss considerations like licensing, recommended hosting providers, and how to use Access runtime and web interfaces for remote data access.

Navigation

Prev: Introduction
Next: Lesson 02

Keywords

Access Seminars, connect access database to sql server online, pass-through query, winhost, access database online, sql server security, access database backup, excel vba sql server, asp web portal, access runtime, access web interface, access backend vs

Subscribe to Overview
Get notifications when this page is updated

Intro

Transcript

In lesson one, we are going to discuss why you would want to connect your Access database to an online SQL Server. We will talk about the pros and cons. Then we will discuss what you need to get started and what they will need to connect to your database.

Why do you want to connect to SQL Server online? Well, if you have ever wanted to use your database in multiple locations, that is reason enough. If you have people working from home, that is another good reason. If you want to allow different people to travel and still have access to the database on the road, there are lots of reasons why you want to have your data online. People anywhere can access your Access database if they have an internet connection.

Remember, the Access runtime is free. As long as they have a Windows PC, they can install the free Access runtime. In addition, you can connect to your database from other platforms. I am going to talk today about using Microsoft Access, of course, and creating a simple web-based interface where you can just use a web browser to view your data. But you can also connect to your database using Excel VBA, an Android app if you know how to do that, even a Mac. There are lots of different ways you can connect your data once the data is stored online.

Let us talk about the pros and cons of working with online data.

A con is that large data sets can take a long time to download. If you have a customer table with 50,000 records in it and you are going to run reports on that, that information can take a long time to transfer to your computer if you pull down all 50,000 records, for example.

However, a pro is also speed. If you optimize your database correctly using something called a pass-through query, then those queries can be performed on the server. The server can process it and send only the data that you need.

For those of you who have been using Access for a while, if you are going to take your old Access database and upgrade it to what we are doing today with SQL Server, it may involve some redesign. You may have to rethink the way you run your large reports and your big queries, or some of your forms. You might not want to pull down all of these records. You may have Access process the information on the server using a pass-through query, and we will talk a lot about pass-through queries in the next couple of lessons.

Next is accessibility. The pro is anyone anywhere in the world can view and edit your database. The con is anyone anywhere in the world can view, edit, and delete your data, so make sure you keep your password safe. I am going to be spending a lot of time - three lessons, in fact - based on security. You are securing your data, making sure people cannot get into it.

Personally, I find even having your data online in SQL Server is still more secure than having it on your network in an Access backend. If all you are doing right now is you have a split database on your network and you have a file share set up with an Access backend, what you are going to be doing today is more secure because you cannot get into that database without the password. In order to give Access users the ability to edit data, you have to give them full control over that share. They have to have read-write access to that file share. Not so with SQL Server. You will actually find that this type of setup is more secure than just a split Access database.

Safety. A pro is your data is stored outside your office, so if the place burns down, your data is already backed up offline. The con is what happens if their data center goes up in flames. Make sure you back up your data regularly. I am going to talk about this in one of the upcoming lessons. You can do manual backups whenever you want to, using the SQL Administrator tool I am going to show you. They also have backup services for a couple of dollars a month. They will back up your database every night, and I strongly recommend that. We will talk more about backups in a bit.

Reliability. If your local server goes down, you can still access your database online. I have had it happen many times where people say, well, the server that we have on the network is down, so we have to move the database somewhere else, restore from backups, but it does not work. That can slow you down for a day or two.

The con is, in the case of an online database, if your internet connection goes down, everybody in the office is also offline. It is usually easier to fix your internet connection problem or have a backup for that. For example, I work for myself here in the office. But if my Comcast internet goes down, I can use my phone as a Wi-Fi hotspot, and then I am back up online. Whereas if the server machine that I have my database on goes down, then I have to either restore the backup to my local hard drive and try to install a SQL Server there. So it is actually easier to deal with the fact that, if your internet connection goes down, you can easily get a backup for that. If you have business class internet, I know a lot of providers also have cell backup for that. If you have cable or the old T1 line or one of those kinds of connections for your internet connection in your office, they have cellular backup options for that as well. In case a truck hits your lines coming into your building or something. Or you could just fire up your phone and get on that way with your web portal. I have had to do that too.

Management. If you have an SQL Server in your office, you have to manage it. You have to install updates. You have to take care of security patches. This way, your SQL Server, the machine, is actually managed and maintained by the IT professionals at your ISP. They handle taking care of it.

A con is you do have less control over the server. There are some things you cannot do to that server. But generally speaking, you should not really need to do most of that stuff. There is some really advanced stuff you cannot do. Me, I am personally happy having them worry about it.

I used to manage my own web server back in the late 90s, early 2000s. I had my own box. I had a buddy of mine who had a server farm in his office because he did basically internet type stuff. So I just rented server space from him. I had to maintain Windows Server and my SQL Server. I had to install security fixes and patches and upgrades. And I still got hacked. I had the US Air Force show up at my house one day and they said, Mr. Rost, your server has been implicated in a denial of service attack on the Pentagon. I am like, what? Turns out hackers from overseas got into my server, and I was fairly up to date with my patches. Bottom line is this way, the security and all that stuff is maintained and the SQL Server is updated by the people at your internet provider. You do not have to worry about that.

Some other stuff. You can handle many more concurrent users than a back-end Access database. You can have 500 people from all over the world working on your database with their Access front ends and your SQL Server back end.

Whereas, if they are all in the same office, that is going to be predicated by your internet speed. If you are using a slow internet connection, that is going to dictate how many users you can have online at one time. On your typical LAN, on your normal Access back-end setup where you have Access as your front end connecting to your back-end tables on a server, I realistically would not have more than 20 people at a time using that database. Even 10 sometimes is cutting it, depending on the speed of your LAN and the speed of your network, but usually 20 is about my cutoff. If someone says they have 100 users, you are going to ask your SQL Server, sorry. I am sure we have all run into this before if you are using a split solution.

You do not have to kick users out of the database to make changes on the back end. If you add fields to a table, they are going to have to close their database, get your update, you are going to send them a new front end or at least relink the tables. We will talk about all this in a bit. But you can still do maintenance changes on the back end without having to kick everybody out. You can run backups without having to kick everybody out. So your database is online 24-7, even while you are working on it. If you make changes to a table, if you add some fields or delete some fields, you can do that while people are using the database and then make changes to your front end, and when you are finished, just distribute your front end.

Con. SQL Server does not support attachments or multi-valued fields. Hyperlinks will get converted to text. But that is not really a con, because if you have taken any of my other classes, I do not like attachments and I never use multi-valued fields. That is not really a con, but I just wanted to mention that in case your database relies on attachments. Big no-no. I have seen attachments corrupt databases. Do not store files, pictures, any of that stuff in your database. I have got dozens of other lessons on that stuff. So if you have any questions, post them below in the comments section and I will point you to the right place.

What do you need to get started?

All you need is Microsoft Access, just one usual license. I recommend a Microsoft 365 subscription so you have the latest and greatest and the best and all the patches and the big bug fixes and all that stuff. If you are using the retail version 2016 or 2019, that is just fine too. Bottom line is you only need one license. The person developing the database, building it, making changes to the design of the database is the only person that actually needs a full copy of Microsoft Access.

You need Windows-based hosting with SQL Server. I recommend Winhost.com. They are my personal recommendation. I am going to spend a whole lesson showing you how to set up an account on Winhost, configure your server, set up your database server. If you want my recommendation, go with Winhost. I will not support any problems or questions you have regarding other ISPs.

I just left GoDaddy. I do not like GoDaddy anymore. My server, I was with them for over 10 years. At first it was great, but toward the end my server was running really slowly. They were trying to blame it on me, my coding, which I know is solid. Their support is awful. They would take days to get back to me sometimes, or you cannot email a technician. Whereas at Winhost, everything is beautiful. I copied the same website over to Winhost and it ran beautifully. GoDaddy was full of bleep. Winhost's service technicians get back to me right away, like within minutes of emailing them.

You need SQL Server to use this class. MySQL is the number two competitor. It is okay. You can use it with Access. I do not support it. I do not use it myself, so do not ask me questions about it. Yes, I believe they also have a SQL Server available for Linux web hosting. But again, I do not recommend that. I recommend Windows Hosting SQL Server. It is inexpensive. We are going to talk about that in the next class. That is what I recommend.

Finally, you need a web page editor if you want to connect to your database using the web. I recommend a program called Edit Plus. Again, I will talk about this a little bit later on. You can use Front Page, Expression Web, whatever web designer you use. I will show you how to use ASP active server pages to connect to your database online. So you can create a portal for your users to view and edit data online. I am going to show you how to connect to it and view the data. I have other classes - my ASP classes teach you how to make editing forms and all that kind of stuff.

What do they need? What do your end users need? All they need, well, first of all, it costs them nothing to get into your data. All you need is Microsoft Access runtime edition. I have a whole other separate set of lessons on this. I will put links down below. It is free. All they have to do is download the runtime edition and install it. Then they are good to go. That is it. You do not have to have a paid copy of Microsoft Access to use an Access database, even an online one.

People tell me, well, I want to use Microsoft Access, but it is cost prohibitive. I have 250 users. No. Only one person in your office needs a paid copy of Access, the person doing the database development. Everybody else, the end users, can use the free copy. It is the same exact thing, you just cannot edit the database, which is what you want anyways. You do not want your end users editing your database.

If you have someone in accounting who wants to write their own queries or design their own data entry form, then they will need a paid copy of Access. It is inexpensive. Get a Microsoft 365 subscription. It is a couple bucks a month. Or if they only need the ability to quickly look up a customer record or look up a sales history, you can build them a web portal in ASP, which I am going to show you a little later on.

That is it. No extra cost. Access is actually a powerful, inexpensive solution for working with data online.

Now that we have that under our belt, we are going to go ahead and get started setting up a Winhost account in the next lesson. Then I will show you how to install SQL Server Management Studio and connect to your database. Then we will actually take an Access database and upload it to SQL Server and connect to it. So get ready. Here we go.

Quiz

Q1. What is a primary reason for connecting your Access database to an online SQL Server?
A. To allow multiple users to access the database from different locations
B. To improve the graphical interface of the database
C. To avoid the need for regular backups
D. To make the database files smaller

Q2. Which of the following is a disadvantage (con) of working with large datasets in an online SQL Server?
A. Reports will generate more accurately
B. Large data sets can take longer to download
C. Queries always run faster
D. Maintaining security is easier

Q3. How can you optimize queries for better speed when using SQL Server with Access?
A. By using a pass-through query that processes data on the server
B. By importing all data to your local machine first
C. By deleting unused tables
D. By compressing your Access database

Q4. Which of the following is NOT a security advantage of using SQL Server online for your Access database?
A. The data can be accessed from anywhere with internet access
B. Users need a password to access the database
C. You have to give full control over your network file share to each user
D. Security patches are handled by your hosting provider

Q5. What is an important consideration regarding accessibility of your online SQL Server database?
A. Anyone anywhere in the world can access and potentially edit your data
B. Only users inside your local network can connect to the database
C. The database is only available during business hours
D. You cannot connect using a web portal

Q6. Regarding backups, what is a recommended practice for SQL Server online databases?
A. Rely solely on the provider's hardware for data integrity
B. Perform regular manual backups or use nightly backup services
C. Backups are not important for online databases
D. Only the developer should make backups once a year

Q7. Which of the following is a reliability benefit of having your database on an online SQL Server?
A. Your data is inaccessible if your office power goes out
B. The database can be accessed even if your local server goes down
C. Only local devices can make updates
D. You must be physically present in the office to access the database

Q8. What is a possible disadvantage (con) if your internet connection goes down when using an online SQL Server?
A. Your data automatically deletes itself
B. Everyone is unable to access the database until the connection is restored
C. The provider will instantly fix local network issues
D. You will need to reinstall all software

Q9. Why is hosting SQL Server with a provider like Winhost considered easier to manage than self-hosting?
A. All management, updates, and security patches are handled by professionals
B. You can upgrade the server hardware for free whenever you want
C. You have unlimited control to make advanced changes on the server
D. Backups are not required with professional management

Q10. What is a main limitation of using SQL Server as the backend for an Access database?
A. SQL Server does not support attachments or multi-valued fields
B. SQL Server cannot process any form data
C. SQL Server can only connect to one user at a time
D. Hyperlinks will always be clickable in SQL Server tables

Q11. For your end users to connect to your online Access database, what do they need?
A. Microsoft Access runtime edition, which is free
B. A full paid copy of Microsoft Access for each user
C. A Linux operating system
D. Permission to edit the database design

Q12. If one of your users wants to create their own queries and forms, what must they have?
A. A full paid copy of Microsoft Access
B. Only the runtime edition
C. Any web browser is enough
D. Microsoft SQL Server Management Studio

Q13. What is required to create a web portal for your users to view and edit data online?
A. A web page editor such as Edit Plus and knowledge of ASP
B. Only Microsoft Access
C. SQL Server alone with no web hosting
D. Excel VBA

Q14. What is a key benefit of splitting your Access database with SQL Server back end?
A. Many more concurrent users can use the database compared to a back-end Access database
B. Only one user can connect at a time
C. It is impossible to make changes without kicking users out
D. All data is stored locally by default

Q15. Which of the following statements about cost is true?
A. Only the developer needs a paid copy of Access, end users can use the free runtime
B. All users must buy a full copy of Microsoft Access
C. Each user must pay a monthly fee to view data
D. The runtime edition of Access is only available for Mac

Answers: 1-A; 2-B; 3-A; 4-C; 5-A; 6-B; 7-B; 8-B; 9-A; 10-A; 11-A; 12-A; 13-A; 14-A; 15-A

DISCLAIMER: Quiz questions are AI generated. If you find any that are wrong, don't make sense, or aren't related to the video topic at hand, then please post a comment and let me know. Thanks.

Summary

Today's video from Access Learning Zone will focus on why you might want to connect your Microsoft Access database to an online SQL Server, and we will explore the benefits, the drawbacks, what you will need to get started, and what your users will need to access the database.

There are many reasons to consider putting your Access database online with SQL Server. If you have ever needed to use your database from multiple locations, or if you have people working from home or traveling, hosting your data online is a perfect solution. As long as there is an internet connection, you or anyone you authorize can access and update your database from virtually anywhere.

Keep in mind, Microsoft's free Access runtime is a huge advantage. Anyone with a Windows PC can install it and use your database as an end user, even without a paid version of Access. Besides Access, you can connect to your online database through a variety of tools and platforms, including Excel VBA, Android apps, or even Mac computers. Once your data is online, it becomes accessible through many channels, including potentially web-based interfaces, which I will be covering as well.

Let us go over the pros and cons of working with an online SQL Server.

First, the cons. Working with large sets of data can sometimes be slow, especially if you are trying to download huge tables with tens of thousands of records. For example, if you have a customer table with 50,000 records and you try to process everything on your PC, it can take a long time to transfer all of that data.

However, with the correct setup, speed can also be a pro. SQL Server allows you to run queries directly on the server using something called a pass-through query. This means the heavy lifting is done by the server, and only the necessary data is sent back to your computer, which greatly improves performance.

If you have been using Access for a while and are ready to upgrade to SQL Server, be aware that you may need to redesign certain parts of your database. Some of your big reports and complex forms may benefit from running those queries directly on SQL Server instead of processing all the records in Access. There will be a lot to discuss on pass-through queries in upcoming lessons.

When it comes to accessibility, placing your database online means that people anywhere in the world can access and edit your data. This is a huge benefit, but it comes with a security concern. Anyone with credentials could potentially modify your data, so keeping your passwords safe is absolutely crucial. I will cover security thoroughly in three upcoming lessons, showing you how to secure your data and prevent unauthorized access.

In my experience, online SQL Server hosting is more secure than simply having an Access backend on your office network. With a split Access setup, users generally need full control over the shared folder, which opens up potential security risks. Online SQL Server, on the other hand, requires authentication before anyone can get to the data, making it much more secure if managed properly.

Another advantage is safety. Your data is housed outside of your physical office, so if anything happens to your facility, the data is already protected. Of course, you need to think about what happens if the data center itself suffers an outage or disaster, so regular backups are extremely important. Both manual and automated backup options are available. I strongly recommend the backup services many hosts offer to protect your database every day.

Reliability is another big selling point. If your in-office server fails, you are often stuck while you try to recover or restore from backups. An online database lets you continue working as long as you have internet. If your internet connection drops, you cannot access your online database, but often that is easier to resolve, and you can always use a backup connection like a mobile hotspot. Many business-class internet providers even include cellular backup options.

Managing a server yourself means keeping up with updates and security patches, which can be a headache. With an online host, professionals handle those updates and security measures for you. You get the benefit of a well-maintained server without the need to get involved with the technical details or put in the work patching Windows and SQL Server yourself.

From a scalability standpoint, SQL Server can support far more concurrent users than a typical Access backend. With Access split-database setups, more than about 20 simultaneous users is difficult. SQL Server, on the other hand, can easily handle hundreds of users across the world, limited only by your network's bandwidth and your host's capabilities.

Another strength SQL Server brings is making changes to your database's structure while people are still using it. You do not have to kick everyone out to run backups or make minor adjustments. Users keep working, and you can distribute changes to the front end as needed.

There are a few things SQL Server does not support compared to Access tables, such as attachments and multi-valued fields. Hyperlinks get stored as text in SQL Server. I do not recommend using attachments or multi-valued fields anyway, as they can lead to corruption. If your database relies heavily on those features, consider redesigning before moving to SQL Server.

So, what do you need to get started? You will need a full license for Microsoft Access to develop and modify your databases. I recommend Microsoft 365, as it keeps you up-to-date, though Access 2016 or 2019 will also work well. Only the developer needs a paid license. Your end users can use the free Access runtime, which gives them the full benefits of interacting with the database without the ability to change the design.

For hosting, you will need a Windows-based provider that supports SQL Server. My personal recommendation is Winhost.com, based on their reliability and support. I will guide you through creating and configuring your account with them in the next lesson. I do not recommend other hosts, especially GoDaddy, because I have had negative experiences with their support and server speed.

You will also need SQL Server, and while other database engines like MySQL are available, I only work with and support SQL Server on Windows hosting. That is what I will be teaching in these lessons.

If you want to provide web-based access, you should have a web page editor such as Edit Plus or similar software. I will show you how to connect ASP web pages to your database so users can view and edit data through a browser. For those interested in building more robust web applications, my separate ASP courses cover creating dynamic data entry forms and advanced interfaces.

As for your end users, all they need is the free Microsoft Access runtime. There is no cost for them to view or interact with your data. Only those who will create queries or build new forms need the full version of Access. For everyone else, the runtime is perfect. If someone only needs to look up information or run reports, you can even build them a simple web portal to access what they need.

Overall, Access remains one of the most powerful and cost-effective ways to work with your data online. Once you have the pieces in place, it is both flexible and affordable for teams of any size.

In the next lesson, we will go through how to set up a Winhost account, install SQL Server Management Studio, connect to your online database, upload your Access tables, and link everything together. Be sure to watch for that.

You can find a complete video tutorial with step-by-step instructions on everything discussed here on my website at the link below. Live long and prosper, my friends.

Topic List

Reasons to connect Access to online SQL Server
Pros and cons of online SQL Server databases
Accessing databases from multiple locations
Access with free runtime edition for users
Connecting to SQL Server from different platforms
Speed optimization with pass-through queries
Redesign considerations when moving to SQL Server
Security differences between Access backend and SQL Server
Importance of strong passwords and data security
Advantages of offsite data storage
Backing up your online SQL Server database
Reliability considerations for online vs local database
Managing connectivity issues and backup internet options
Management and maintenance differences for SQL Server
Concurrent user capacity with SQL Server
Making backend changes without disconnecting users
Limitations of SQL Server with attachments and multi-valued fields
Requirements to get started with Access and SQL Server
Choosing a hosting provider for SQL Server
Cost considerations for Access licensing
Web portal access using ASP and web editors
End user requirements with Access runtime

Article

Connecting your Microsoft Access database to an online SQL Server has many advantages, especially if you want to work with your data from more than one location. If you or your team members work from home, travel, or simply need remote access to your database, putting your data online becomes a great solution. As long as someone has an internet connection, they can get into your Access database from anywhere.

One benefit to keep in mind is that Microsoft Access provides a free runtime version. This means anybody with a Windows PC can install the free Access runtime and start using your database. You are not limited to only using Access either; your database can be accessed in different ways, such as through a web browser, Microsoft Excel, or even from other platforms, provided you know how to set them up to connect. Once your data is online, you have the flexibility to reach it in many different ways.

Of course, there are pros and cons to working with online data. For instance, if your database has very large tables, downloading all records can be slow. As an example, if your customer list has tens of thousands of records and you try to open the entire table, it may take a while to download that much information to your computer. To avoid this, you should optimize your database by sending queries to the server using what is called a pass-through query. This way, the server does all the heavy lifting, processes your request, and sends back only the data you actually need. This helps address speed concerns, as you are no longer pulling down large tables all the time.

Moving an existing Access database to use an online SQL Server will likely require some redesign. In Access, you might be used to pulling down entire tables or running big reports and queries locally. When you upgrade to an online setup, you will need to change how some reports and queries work so they process on the server. Many adjustments simply involve learning to rely more on server-side processing, using pass-through queries, and thinking about how much data you really need at one time.

Accessibility is both a big advantage and a potential risk. With your data online, anyone you authorize can connect from anywhere in the world. However, that also means keeping your passwords secure becomes even more important. If someone else gets access, they might be able to view, edit, or even delete your data, so you need to take security seriously. You will want to follow security best practices, including limiting who has full permissions.

Even so, having your data online is often more secure than running a split Access database on your network with an Access data file as the backend. With Access, users typically require full control over the shared data file, which can easily lead to accidental data loss or damage. An online SQL Server requires a password and can limit access controls much more effectively. You are also less likely to face problems like someone accidentally deleting your whole database.

Another benefit of using an online server is safety in case something happens to your office, like a fire. Your data lives offsite, so if your own computers are lost, you still have your database available elsewhere. However, you should back up your online database regularly, just as you would any important data. Manual backups can be created whenever needed, and many hosting providers also offer automatic nightly backup services for a small additional cost. Relying on these backups gives you peace of mind that your data is safe.

Reliability is another important advantage. If you are currently using a local server and it goes down, everyone who needs the database is dead in the water until you recover it. With an online server, your data is still available wherever you have internet access, and you are not tied to any one physical device. The downside is that if your office internet connection goes down, you are offline until it comes back up. Generally, it is easier to get a backup internet connection than to recover a broken server. Many businesses also use cell network backups, so if their primary line goes down, their internet fails over to mobile internet, keeping everyone connected. For individuals, using a phone as a Wi-Fi hotspot is an easy backup solution.

Managing the server also becomes simpler. If you run your own in-house SQL Server, you are responsible for installing updates, applying security patches, and keeping up with maintenance. When you use a database hosted by a provider, the IT professionals at that company take care of management and maintenance. This takes the burden off you, so you do not have to worry about keeping up with all the technical details or about security vulnerabilities.

There are some trade-offs in terms of control. You might not have administrative rights to every feature of the hosted SQL Server as you would on your own private server, but in most cases, you will not need that level of access. Most day-to-day database tasks can be done easily, and the convenience of letting someone else handle the technical management is often worth it.

An online SQL Server can support far more simultaneous users than an Access backend. If you only have a shared Access database sitting on a file server, you might find things slowing down or even breaking with more than a dozen or two users at once. The online setup, meanwhile, can handle hundreds of users across the globe, depending on your hosting plan and the speed of your internet connection. This makes it much easier to scale your database use as your organization grows.

Another advantage is that you do not have to kick users out of the database for maintenance tasks like adding a new field or taking a backup. Maintenance can be done while users are still connected, and your database can remain online all the time. When you make changes to the database structure, you simply update your Access front end and send that update to your users.

There are a few technical limitations to keep in mind. Online SQL Servers do not support Access attachments, multi-valued fields, or hyperlinks as you might be used to. These fields are either converted to text or not supported at all when you move your tables to SQL Server. Generally, this is a good thing, as storing files and attachments directly in a database is not recommended. Instead, keep files outside the database and link to them as needed.

To get started, all you need is your usual copy of Microsoft Access. Only the person developing and managing the design of the database needs a paid license. All your end users can use the free Access runtime, which lets them open and run your database without making design changes. This means that even with a large number of users, you do not need to buy many copies of Access. Most users just need to enter and view data, so the runtime is perfect for them. If someone wants to design their own queries or modify forms, then they would need a paid Access license.

You will need SQL Server hosting from a provider that supports Windows-based SQL Server. There are many providers to choose from, and you want one with responsive technical support and good reliability. Avoid providers whose service is slow or who are difficult to reach for help.

If you want to provide access to your data online through a web browser, you will also need a web page editor. With a program like Edit Plus or any preferred web design software, you can build simple web interfaces using ASP that connect to your SQL Server database. This lets users look up data or even perform simple edits from anywhere, all through a web portal.

For your end users, it really could not be easier or more affordable. All they need is the free Access runtime, which they can download and install. They do not need a paid version of Access to use your database, even online. If you have a team of hundreds, only you as designer or developer need to pay for the full Access program. This makes Access a very cost-effective solution for sharing data online.

Getting started is actually straightforward. First, you will set up your hosting account with SQL Server, then use the management tools provided to create your database and configure user access. After that, you will move your existing Access tables into SQL Server (a process often called "upsizing") and link them to your Access front end. From there, your users can immediately start working online. If you want to go further, you can even build a simple website that connects to your database and lets users log in and view or update data using only a web browser.

With this foundation, you are set to provide modern, secure, and accessible data solutions to your team, clients, or organization using Microsoft Access and online SQL Server hosting.