Connecting Access Front End to Remote SQL Server

I have a web site on a remote, shared host with a bunch of individual
Access databases.  I want to upsize my databases from Access to MS SQL
and have some questions.

I update some of my Access databases through web-based content
management systems.  Other databases I update locally (through a bunch
of Access forms) and FTP them periodically to my web site.

I want to be able to switch my databases over to SQL, store them on a
remote SQL server and continue to update them via a local interface
(forms in my Access front end.)  (1) Could someone recommend a good
tutorial for this?  I'm not sure where to begin.

For some of my databases, I also want to continue to allow people to
update the database via my web-based content management systems and at
the same time use an Access front end for my local users.  (2) Are
there any problems with both interacting with the database via the
Access front end and my web-based content management system at the same
time?

(3) Since my web site (and SQL Server) is on a shared host, are there
problems I might encounter?  I am able to connect to my host's SQL
server via the Enterprise Manager installed on my local MS Small
Business server.  (4) Will my Access front end also have to reside on
my local Small Business server, or can it reside on my local client
computers?

"Rupe" <clewis@jazztimes.com> wrote in message
news:1114120860.405098.221430@l41g2000cwc.googlegroups.com...
>I have a web site on a remote, shared host with a bunch of individual
> Access databases.  I want to upsize my databases from Access to MS SQL
> and have some questions.
>
> I update some of my Access databases through web-based content
> management systems.  Other databases I update locally (through a bunch
> of Access forms) and FTP them periodically to my web site.
>
> I want to be able to switch my databases over to SQL, store them on a
> remote SQL server and continue to update them via a local interface
> (forms in my Access front end.)  (1) Could someone recommend a good
> tutorial for this?  I'm not sure where to begin.

Access has an upsizing wizard, but that's about the limit of my Access to
MSSQL conversion knowledge. You might want to post in an Access group to see
if you get a better response.

>
> For some of my databases, I also want to continue to allow people to
> update the database via my web-based content management systems and at
> the same time use an Access front end for my local users.  (2) Are
> there any problems with both interacting with the database via the
> Access front end and my web-based content management system at the same
> time?
>

In principle, no - MSSQL will use locking to prevent people modifying the
same data at the same time (if that's what you mean). You should probably do
some reading up on transactions, if you haven't already.

> (3) Since my web site (and SQL Server) is on a shared host, are there
> problems I might encounter?  I am able to connect to my host's SQL
> server via the Enterprise Manager installed on my local MS Small
> Business server.

If you can already connect with EM, then you should be fine (as long as your
users can connect also). You might have permissions issues if your ISP only
allows you to have one login, as generally you don't want your users to have
the same access you do.

> (4) Will my Access front end also have to reside on
> my local Small Business server, or can it reside on my local client
> computers?
>

If you can connect to the remote server from your client PCs, then you can
use the Access front end from there. You might have to check your firewall
configuration first:

http://support.microsoft.com/defaul...kb;en-us;287932

Simon


Simon