Need Lots OF Help

RyanW2013

New member
Local time
Today, 14:49
Joined
Apr 16, 2012
Messages
3
I am a beginner at this. I work for a church, and using access, we have all of our members info on it. But, we want to know how we can set it up so one of our pastors can log into the database at home and work on it. Even if we have to use SQL and put it on our website w/ password protect. We DO want the database to be protected.
 
Why not get a dropbox.com account and set it up on your Church PC and your Pastors PC. Put your db in the dropbox folder you want to share. Dropbox is free for up to 2Gb.
 
I think Dropbox is risky although I haven't tried. Essentially it's just a file sync service afaik. So this would be fine if only one person is ever working on it. But two people at the same time is going to be interesting especially if they make changes offline. Have a read here for more comments.

I would think a remote desktop would be the easiest solution to deploy making sure each user only uses their own front end. Again I'm no expert.

Chris
 
Dropbox is not an online db. Each user works on a local copy on the desktop, and it just overwrites whatever resides in the online dropbox when syncing afterwards. he latest copy "wins". The users cannot simultaneously work in the same db. One at a time can work, but not simultaneously.

Remote access can be through remote desktop as Stopher writes. That can require setting up of router. Alternatively there is a whole plethora of apps like LogMeIn, gotoAssist, and Teamviewer that allow remote access to a running computer. With some fiddling, one can even wake up a computer from stand-by (not hibernation) via WAN.
 
I agree with Spikepl and Stopher, however I offered up this suggestion as an inexpensive means and figured that if the pastor was working from home then it would be during off hours. Maybe a bad assumption.
 
I was just wondering if it was possiable to have it uploaded to our website so it can be access able to those that have the login to the database.
 
The Access application can be set up to link to the SQL Server tables on your website rather than to a Jet/ACE database on your server. The change is relatively easy. If the tables already exist on the server, just delete (after backing up of course) the links to the Jet/ACE BE and then relink to the SQL Server BE. If the tables are not there, you can use the upsizing wizard to define them and load them with the current data. I doublt you'll have performance issues because you probably won't have more than a few thousand rows in any table. However, for those of you reading this who have larger datasets, some changes will need to be made to your FE application to obtain any speed benefits from SQL Server or even to just keep from slowing your FE to a crawl which can easily happen if your FE uses forms bound directly to tables or bound to queries with no criteria. The one thing your DBA will hate to see is an Access app sitting with an open form sucking down all the data from a server-side table. So, read up on client/server techniques and always bind your forms to queries that select the absolute minimum number of rows and columns.
 

Users who are viewing this thread

Back
Top Bottom