multiple location problem

[gregd]

I am new to building access solutions. And I have a basic question.
I am using access 2010.

If I have 2 people that need to use a tool.
At 2 different locations in my company.

I believe there are 3 solutions to a multiple location problem.

1)
Create a web based database and deploy to sharepoint.

2)


Create a database, post on IIS server, create php or asp pages to read write to the database.

3)
Create a database on a network share.
Create a local access db that links to the tables on the network share.


Are there any other options I am missing?
How bad is choice 3? If the network is stable would the end access application be stable? Etc...

thanks

[June7]

I use option 3. Database is split and has about a dozen users. Each user has their own copy of frontend on their local work station. Every once in a while a local copy gets corrupted and I have to force a replace but otherwise performance is acceptable.

I have heard VPN mentioned as an option but also heard connectivity is unreliable.

[gregd]

Thanks for the input June7.

In your setup, do each users work station ms access copy get linked to a networked database?


Also,
For option 1, (if anyone knows)
After deploying the db to sharepoint, can I then update that db from access? Just like an initial deploy. But updating the db?

thanks

[redbull]

Option 3, 100% is the way to go.


I use this method to distribute my applications to a user base of over 100 people. Here is a break down of how it works.

I have a folder on the shared drive, it holds my MDE file, my background image as well as a .vbs file

I email new users a link to the vbs file, they click it and select run.

The vbs file then downloads this folder to their PC, including the vbs file. So now they have a local copy of all of these files.

It also installed a jazzy shortcut icon I created on the desktop. It looks nice and this is how they will open the application from now on.

When the user opens this icon it is really opening a local copy of the vbs file. It does a quick date modified check.
If there is a new copy, it will download the new .mde file from the shared drive.
If the date modified is the same, it will just open the access application.


----------- Thats it, Now I have special situations that require the .mde file on the shared drive to be "virgin" The reason is I have an on load event that establishes table links to numerous locations around the company. But that is how I manage my application.

If you need a hand let me know, things are slow around the office today.

[June7]

Review
http://office.microsoft.com/en-us/ac...010342026.aspx
http://databases.about.com/od/tutori...itaccessdb.htm

Here is how I manage split db http://forums.aspfree.com/microsoft-...ue-323364.html

[gregd]

Thanks for the help. I have a lot to absorb.
I don't see a select best answer. So I just added to the reputation