WinHost (and other web hosts) can host an Access database file, but the important distinction is how it's being used. In a web hosting environment, the Access database sits on the same server as the website, and the web pages or server-side scripts connect to it locally. In other words, the website can use the Access database because the database engine is running right there on the server next to the file. That's very different from trying to connect to that same file directly from your desktop Access front end over the internet.

Access is a file-based database system that expects direct network file access, like opening a backend from a shared folder on a LAN. Web hosts don't provide that kind of low-level file connectivity, locking, and performance support over HTTP or FTP. Even if you could map a drive or force a connection, it would be extremely slow and very prone to database corruption, especially with multiple users. So while an Access file can live on the web server for website use, you generally can't use it as a remote backend for distributed Access front ends.

In fact, I used to teach this in my really old FrontPage classes, and that's how I got started getting my database online. You upload the mdb file, and then you can connect your ASP pages to it, but it's not the quickest thing. And you definitely can't connect to it from your local database here.

If your goal is to work with your data remotely, the right solution is to move the backend to SQL Server. That's exactly what it's designed for: secure, concurrent, client/server data access over the internet. WinHost is actually a fantastic option for that. They provide solid SQL Server hosting, and it's the platform I personally use when teaching my Access to SQL Server online course.

Thank you Richard for clarifying that.
I do have all of your SQL training videos and seminars.
I am really looking forward to this new SQL seminar that you are starting now.

Thank you and keep up the great work.