Stand alone access app instead of multiple db at diffrent locations.

[jinalpatel]

We have access database which is stand alone application. It is sitted at 21 different locations including one main office. Every month the transactions are copied in to disk and sent to the main office.(sounds so outdated but it is like that!!). Then we run that cd to copy those transactions to the main office database.
Each location has not more than two users who are usng this database.

Question: is there any way we can built the access application which is not stand alone? I mean everybody can access the same database.??
I have one idea to put it on a server and give it a web front end(but we are kinda out of burget for that), Is there any other way which is not so costly?

I would appreciate any help on this topic

[Krandor]

A web page would be the simplest (and actually cheapest) way to do what you want to do.

Remember first that doing it the current way is also costing a lot of money. Every month someone at each of the sites has to make a copy of the data and then someone has to load all that data into the main database. That is a lot of labor that the company is paying for.

A website that is tied to a database can be put up in as little as a week or less. Everything depends on how complicated the application is.

If you do go with a website, make sure to password protect the site so only employees can get in. That way you protect your company data.

I've made lots of these sites before so if you want some further help, send me a private message here to me (Krandor) and I will see what I can do.

[NeoPa]

Bear in mind that a web page with a simple password is very rarely ever used by large companies to share company data on. Not unless that data is fundamentally expendable.

A simple password on the internet is a bit like locking your front-door with a bicycle padlock. Not remotely adequate.

Clearly, the data that is to be shared is important in making your decision, but if you can't afford to lose it, or even share it, then making it available on the web behind a simple password is a problem of your own making.

[missinglinq]

Also realize that making a web-based front end requires a developer with experience using a language such as ASP or PHP; it can't be done directly using Access/VBA.

Linq ;0)>

[MindBender77]

Neopa and Linq make very good points. However, might I suggest developing an Intranet site only accessible from your company's server. This should prevent exposure to eyes that are outside of your company.

Bender

[NeoPa]

Hard to get 21 different sites to access the same intranet unless they're linked via some sort of network though Bender.

I doubt the question would need to be asked if that were available anyway.