OK I've read a few solutions, but I'm not sure what I need. My company uses Access to keep up with mostly everything. Products, orders, shipments, invoicing, you name it. However, we are spread out geographically and we don't have a windows server at my office.
So, I'm looking into putting Access online in some fashion so that we can all access the same data, but use Access itself as a frontend. I'm interested in knowing the best way to do this. Can I get a shared windows hosting plan with someone like ixwebhosting.com and configure the DSN to connect the online version to the not-online version? Or do I have to convert my database to SQL Server, upload it, and then somehow connect access to the online version?
The ultimate goal is to have just the DATA online where we can all access it. But I'm not knowledgable enough in PHP, ASP, or other languages to build an online application, so it seems that using Access as sort of a front-end would be preferrable. But all the talk of OLE DB, ADO, JET, SQL SERVER, ADP, etc...this is really confusing to me. I need some help understanding my options here and finding a solution. Web hosts are clueless as to whether or not they even support Access as a frontend as I've noted.