I looked at the template. It uses some of the typical poor design techniques evidenced in earlier versions. It is completely macro based which makes it difficult to modify.
It also may be a web template because I can't put any object into design view to see what's behind it
@smstothrs,
I'm not sure what you think you need to spend for a custom application but you will need to be sitting down when you get the quote. Look at commonly sold complex applications such as QuickBooks (an accounting package sold in the US which has many variations to make it suitable for different types of businesses.) A basic, generic version will sell for ~ $300 per user. If you need multiple licenses, there are packages that reduce the cost per seat. Dozens of developers have worked on this package for 20 years and the development cost by now is probably in the 10's of millions of dollars. And yet, you can get all this functionality for as little as $300. That's because there are millions of people who purchase the product every year so the cost of development and maintenance is amortized over the entire user base. If you were to develop this from scratch today, it would probably cost close to a million dollars and that is assuming that you used QuickBooks functionality as your model and just copied its look and feel and made assumptions regarding the underlying schema. If you were to start with nothing but a bright idea, you would probably spend closer to 3 million.
That's an extreme case because QuickBooks is a full featured accounting application and is very complex and due to its nature requires significant testing and version control.
For your own version of this template, you are looking at a minimum of $2,000 and more realistically $5,000 but could easily spend $50,000.
If you get an offer from someone to do it for $500, run as fast as you can. You are dealing with someone who doesn't know anything about development and probably also nothing about Access. You will end up spending an enormous amount of time with little to show for it.
Also, keep in mind that Microsoft has deprecated Access Web Apps so unless you are hosting it yourself on your OWN website where you can control software versions, all of them will stop working in April I think.
There is a desktop version of this app but I don't think it is as fully featured. You should try that one and see how it is.
Access is natively multi-user so any app you develop can be shared by multiple users. There are best practices that you should adhere to to avoid corruption issues though. For example the app should ALWAYS be split into two separate databases. The FE (front End) contains forms, reports, queries, macros, code, and LINKED tables. The BE (back end) contains only tables. Then EVERY user has his own personal copy of the FE stored on their local C: drive and linked to the shared BE which is located in a shared folder on a network drive. So in this best practices configuration, only the BE, which holds the data is shared.
If everyone works in the office and connects to the same LAN, this will be all you need for multi-users. If some workers will be remote either all the time or just some time, you will need to use Citrix or RDP. You can run either on your servers and they will allow people to connect to the local Access application via the internet. We can go there if you need to and discuss those options in more detail. So you will still have options for data sharing remotely, it is just that you CANNOT do it with Access Web Apps. They are dead.