Connect to back end over the Internet?

[Andy]

Hi,

I have set up a network of front end databases connecting to a back end on a
server.

I'd like to set up a front end database to connect to this back end over the
Internet.


Any suggestions?

Do I need to buy another product?

Do I need 3rd party software?


Thanks

 

[Albert D. Kallal]

Hi,

I have set up a network of front end databases connecting to a back end on
a
server.

I'd like to set up a front end database to connect to this back end over
the
Internet.


Any suggestions?

Do I need to buy another product?

Do I need 3rd party software?

I have an article about this issue here:

http://www.members.shaw.ca/AlbertKallal//Wan/Wans.html

 

[Paul Shapiro]

I have set up a network of front end databases connecting to a back end on
a
server.

I'd like to set up a front end database to connect to this back end over
the
Internet.

Any suggestions?
Do I need to buy another product?
Do I need 3rd party software?

An Access .mdb is a file-server database, and is not designed to be used
over a WAN. Each workstation independently writes to the database, so any
communication interruption potentially corrupts the db. Performance would
also be awful unless it's a very small db.

Standard approaches are either using a client-server db for the backend,
like SQL Server, or using a Terminal Server on the LAN so remote users are
"working" on the LAN.

 

[golfinray]

See this article:
http://www.members.shaw.ca/AlbertKallal//Wan/Wans.html

 

[Andy]

Thanks Golfin' Ray,

It provides a lot of food for thought...

 

[Andy]

Thanks Albert,

Your article has saved me soooo much time.

It looks like SharePoint is the way to go for me at the moment.


Thanks again for a superb article,
Andy

 

[Andy]

Thanks Albert,

It's a very well written and informative thanks.

Andy

 

[GBA]

In addition to AK's article and PS's input - - keep in mind that going to
Sharepoint doesn't magically change the WAN scenario - if the Access FE and
Sharepoint server are on the same LAN it will be ok - - but if they are
geographically separated then you still have the same issue. Here are my
thoughts on this topic in what I consider to be pragmatic:

Generic advice on remote Access database options where one has only generic
internet and not a high speed private WAN with Terminal Services capabilities…

Option 1 – stay with Access’ embedded replication feature (if .mdb format –
not available with .accdb 2007 format) presuming you can co-locate or vpn
them together.

Option B is to go with web architecture. find a web developer - turn over to
him/her your Access db for them to look at as the prototype design...and get
their quote. You will pay to have them develop it and then there will be the
recurring for the hosting company...

Option III is the AccessTables.com service; this allows everyone to operate
a copy of the Access db locally and then you send in the tables - they
consolidate/replicate all the data - - and return to everyone a consolidated
set of tables. Is great as long as the requirement is not for instantaneous
shared data. If periodic updates is sufficient and the user base are all
part of a team - this can be a good solution.

Option 3.5 is an online commercial db service - I would recommend
DabbleDB.com Intuit also has a product : QuickBase - but it is quite
pricey and intended for corporate users. Dabble is very reasonably priced
and pretty cool. When using a db service you are in their sandbox and must
live with the features and look they offer; the redesign using Dabble is a
bit of work & learning and there is definitely missing many features one
takes for granted in Access.

Option 5 is to have users get into Access using a commercial VPN service
such as www.GoToMyPC.com. This will also have a monthly fee. The PC must
always be on for the user. A bit of a latency/lag experience. Only one user
can log on at a time...and, importantly, the log on user will have the
ability to see everything on the PC - not just the Access application....

No right or wrong per se – just right or wrong for one’s situation…finding
the right tool for the job…or redefining the job for the available tool…..