Re: Split DB over the internet with SQL backend?
- From: "Anthony England" <aengland@xxxxxxxxxx>
- Date: Sat, 22 Apr 2006 23:33:59 +0100
"Mark 123" <none@xxxxxxxx> wrote in message
news:TVd2g.15756$JZ1.605448@xxxxxxxxxxxxxxxxxx
I just read at
http://groups.google.com/group/microsoft.public.access.forms/browse_frm/thread/766ba7b493eacb63/8a7d5504ee848c21?lnk=st&q=migrate+access+97+to+access+2007&rnum=1#8a7d5504ee848c21
that if you have a spilt db using SQL server rather than jet, the
front-end's can connect to the backend SQL server over the internet.
Has anyone had experience with this?
We are thinking of migrating an commercially sold Access97 runtime app to
Access 2007 and if this is true it may well pay to redo the backend in SQL
Server so users can use over the net if needed. What other
upsides/downsides
are there to this?
Do 'little' end-users have to be rocket scientists to install and maintain
SQL server? $? Currently they only have to place one MDB backend file on a
shared fileserver. Some of them only have 5 PC's networked in their
business. Others have 500.
TIA
I have done this without any problems with speed or reliability. I went to
a web host (http://www.fasthosts.co.uk) to provide space on a SQL Server
database which gave me some control over the setup (eg able to add logins)
but not total control of the machine.
It was set up with port 1433 open and no vpn, so provided you knew an ip
address and username/password you could sit down anywhere in the world and
access the data. This configuration is not the most secure (the data was
not overly precious) and although I can't prove the data was not looked at
by unauthorised people, I doubt it very much and I am sure it was not
tampered with in any way.
If the sole purpose of the exercise is to enable the database over the web,
then moving to SQL Server may not be the best option. There are other ways
such as Terminal Services or PC Anywhere where users could remote control
another machine to access the database. This has the advantage that you do
not need to modify your coding in any way at all, and any questions of
setup/security are now someone else's problem.
If, however, you think you may need to build up some experience with SQL
Server in any case, then you might want to install it on your local network
and get the db up and running and tuned for SQL Server (you could
potentially do a lot of re-coding for this). Once the app is up and
working, you could build a setup module which creates a new copy of the
database and any other initialisation.
I would guess that customers with 500 pcs might already have their own SQL
database together with a salaried db administrator who would be quite happy
to look after the database. For smaller customers, you could do the setup
and keep a watchful eye over it and charge for this service.
.
- Follow-Ups:
- Re: Split DB over the internet with SQL backend?
- From: (PeteCresswell)
- Re: Split DB over the internet with SQL backend?
- References:
- Split DB over the internet with SQL backend?
- From: Mark 123
- Split DB over the internet with SQL backend?
- Prev by Date: Re: Problem with opening form by timer event
- Next by Date: Automating Word Mail Merge - confirm data source problems
- Previous by thread: Re: Split DB over the internet with SQL backend?
- Next by thread: Re: Split DB over the internet with SQL backend?
- Index(es):
Relevant Pages
|
|
