Re: Connect to Access Data from various regional locations

From: Sylvain Lafontaine ("Sylvain)
Date: 11/28/04 

Date: Sun, 28 Nov 2004 15:01:33 -0500

Split your Access database into a Frontend (FE) with tables linked to a
Backend (BE) and use MSDE as the BE instead of Access. When using MSDE
instead of Access as the Backend, all you will have to will be to add the
parameter "dbSeeChanges" here and there. For example, instead of writing:

    Dim rf As DAO.Recordset
    Set rf = qf.OpenRecordset(DAO.dbOpenDynaset)

you will have to write:

    Dim rf As DAO.Recordset
    Set rf = qf.OpenRecordset(DAO.dbOpenDynaset, dbSeeChanges)

Finding where to put these changes will be easy because Access will generate
an error and tell you where the first time you will try to execute a piece
of code without this parameter.

There is a wizard to split your database into a FE and a BE; so except for
the small change of code above; there is nearly no work to do at all.

Finally, if you don't have a static IP address for the machine where the
MSDE database will be located, you may use a service like www.no-ip.com .
This will enable you to use nearly any machine as the database server;
without the need to buy space. The only required thing to do will be to
make that the port number 1433 isn't blocked by a firewall and correctly
forwarded if the machine is connected to the internet via a router instead
of having a direct connection. (Many providers will offer MSDE or
SQL-Server as part of their offering; however, many of them will also block
the port 1433 for a « better » security; so you cannot use them for this
kind of service.)

Total cost: 0$.

S. L.

"Paul Proefrock" <proefrock@NO_heartlandgroup_JUNKMAIL.com> wrote in message
news:ec8kj1W1EHA.3120@TK2MSFTNGP12.phx.gbl...
> We are a non-profit organization that keeps all our membership info in an
> Access Database. We would like to be able to put the back-end(data) in a
> centralized location and have various users connect, real-time, to update
> their portion. Users are located in Florida, New York, Missouri and
> Nevada.
>
> We do not have an organization owned server and we buy space for our
> hosted website and email.
>
> We don't want to go to Data Access Pages (certain access functions not
> supported) or ASP, (Non of us are proficient in ASP), at least not yet. I
> understand that Access only likes to connect to data when on a true
> network.
>
> What various solutions may be available to us? VPN, hosted server, ? ? ?
> Mind you, we are a non-profit so money/cost is an issue.
>
> I would appreciate any ideas on how to accomplish this
>
> Thanks
>
> Paul P
>

Relevant Pages

  • Re: Connect to Access Data from various regional locations
    ... Backend and use MSDE as the BE instead of Access. ... There is a wizard to split your database into a FE and a BE; ...
    (microsoft.public.access.dataaccess.pages)
  • Re: Data corruption with SQL server installed
    ... I noticed that the rogue Primary key that appeareed with the .AddNew method ... The installation of MSDE comes after the installation of MDAC 2.8, ... you could create an empty database and import everything into ...
    (microsoft.public.access.tablesdbdesign)
  • Re: Put database on Internet
    ... > Once you will be able to connect to MSDE or to SQL-Server, ... > and ADP in the same time as frontends to your database. ... >> will be able to serve as SQL server. ...
    (microsoft.public.access.dataaccess.pages)
  • Re: Connect to Access Data from various regional locations
    ... All users will be connecting via broadband. ... When using MSDE ... > Dim rf As DAO.Recordset ... > There is a wizard to split your database into a FE and a BE; ...
    (microsoft.public.access.dataaccess.pages)
  • Re: Using vfoledb with webservices?
    ... MSDE database can handle at full speed. ... capabilities of Microsoft Access or, in the reasonable opinion of Microsoft, ... and unless Licensee Software requires your customers ...
    (microsoft.public.fox.programmer.exchange)
Loading