Best,cheapest and fastest method to share database

[kinneretaccess]

Hi all, i have a company which is working with access and the database is shared via local network. I want to be able to connect a remote computer


(even from abroad) and have MS access run the same way it does right now. I have created an SQL server data base but when you try to use it its so slow its impossible to work. (used this tutorial http://holowczak.com/migrating-a-mic...to-sql-server/ )

The whole file they are working with is about 50 mb (Tables, froms, queries etc...) so i need a reliable, fast and cheap way to share the database among all the computers i wish to connect.

I do not understand a lot of technical stuff so references to tutorials would be best if possible.

Waiting for your help,
Thank you

[orange]

Readers need more info about your database and set up to offer focused advice.
How many concurrent users? is the database split? What is the subject matter/business involved?
Do you have someone "technical" available to you/on staff?

Here is a link to a "similar" request for remote users to access a database. See post 13 for some options.

You don't usually get Best,cheapest and fastest at the same time.

[kinneretaccess]

Thank you for your replay!
Around 8 users, the database is split (and shared via local network), tour company (mainly using access to organize clients in groups, sending bills etc). Unfortunately I am the most technical person.I don't need the best option, only one that works as fast as local network and doesn't cost much.

I have around 5 users now on the local network, need only 3 users to share the database with.
The critix or RDB sounds good if secure.

[orange]

I don't have personal experience with Citrix, but others on the forum(s) have.
I did find this link via a google search

[CJ_London]

Similar to citrix, use a web based terminal server hosting a sql server back end. Security is handled via the remote desktop connection/login. Pretty fast since the only network traffic is screen updates (unless you copy data to a local drive)- and will work with other devices such as apple. You don't need additional access licenses since you can use access runtime which is free

If you have the budget for sql server (which does feel a bit OTT for 5-8 users), then you should have the budget to do it this way.

[kinneretaccess]

Similar to citrix, use a web based terminal server hosting a sql server back end. Security is handled via the remote desktop connection/login. Pretty fast since the only network traffic is screen updates (unless you copy data to a local drive)- and will work with other devices such as apple. You don't need additional access licenses since you can use access runtime which is free

If you have the budget for sql server (which does feel a bit OTT for 5-8 users), then you should have the budget to do it this way.

Sorry i need some more clarification. how does this differ from the method i used above? (http://holowczak.com/migrating-a-mic...to-sql-server/ ).
I havent tried critix yet and am not sure how to approach it?
Some writen guide to any method would be very helpfull, I am clueless as to what to do on my own

[CJ_London]

Both front end and back end are on the same server so performance is much the same as if the back end is on your local drive. Probably not a solution for you but google teamviewer to try for a similar experience

[NoellaG]

Have you thought about using sharepoint lists?
https://technet.microsoft.com/en-us/...04.access.aspx

[orange]

Some writen guide to any method would be very helpfull, I am clueless as to what to do on my own

Have you tried Google and/or youtube for info on Citrix?

[kinneretaccess]

I am looking everywhere and I just dont know how to proceed forword. How do i set up a sharepoint? how do i use critix?
sorry i am completly clueless.

[ArviLaanemets]

Does you company have a terminal server in your local network? When yes, then:

1. Create domain user accounts for people needing to connect to database remotely (in case they don't have it);
2. Create user profiles on terminal server for them;
3. Create datasource(s) needed to connect to backend database on terminal server;
4. Save database frontend into profile for every user (on desktop, in document's folder, mapped user drive etc.);
5. Allow VPN or SSL connection for domain user(s) from outside to Terminal Server (there are several ways for this - consult your network administrators);
6. Install VPN/SSL client or shortcut for web-based VPN into user(s) computers (again, there are several different solutions available, and probably you better consult your network administrators);
7. The user logs from anywhere into terminal server in company's LAN and works like he/she is there in person, with rights and accesses defined for this user in domain. All data connections, queries, procedures are started and running on local network, over internet only screen image and keystrokes are sent.