SQL Server is far better. SharePoint is a pita. As Richard has mentioned in a few areas like THIS.

Yeah, I prefer SQL Server. As far as your images go, as long as they're on a public-facing drive/server, then you can still link to them. I upload mine via ASP Upload to my webserver.

I am currently using SharePoint and do not recommend it. I have a win host account that I will be moving my production database to. However, I have discovered this can require some adjustments to your current code. I have completed Richards SQL seminar but still find it to be a challenge. But, even with the difficulty I have encountered, I firmly believe the effort will be worth it.

Hi Richard. For SQL server, do I need to distribute a front end to each user or is it enough with one in the database? If I have 500 users all over the country then it is unpractical to distribute 500 front-ends.
Best
Masih

Hi Masih,

I have about 50 users scattered all over the state. I use Richard's amazing "Access Updater" Access Updater to distribute my 2 applications and keep them UpToDate.

There is no escaping multiple front ends for your users. For the initial installation, I email my users a zip file with short video instructions on how and where to unzip it. That is it.

When it comes to your front ends, yeah, everyone has to have a copy and like Sami says, you can use my Access Updater or to update them as long as they have a shared server drive letter (Z:) or server name (//SERVER). You can do this over a VPN (is that what you're using, Sami?). The only other alternative would be to develop a web-based front end, but then you lose the power and ease of design that Access provides.

We have shared drive on the network x:

Perfect.