Re: Put database on Internet

From: Sylvain Lafontaine ("Sylvain)
Date: 12/22/04

  • Next message: DP: "Elementary help?"
    Date: Wed, 22 Dec 2004 13:14:54 -0500
    
    

    I forgot to say that your best option might be to simply use a VPN and
    Terminal Services. The relevant administrator/technician at your college
    should be able to tell you is you can use this option.

    S. L.

    "Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam please)>
    wrote in message news:%23do4iBF6EHA.1204@TK2MSFTNGP10.phx.gbl...
    > If you are going to use a public IP address, then your best bet will be to
    > forget about ASP and use MSDE or SQL-Server as the backend, with either an
    > Access MDB file using linked tables as the front end or an Access ADP
    > project. You must make sure that the port 1433 is not blocked by
    > firewall. You can find examples of connection string at the two following
    > web sites: http://www.able-consulting.com/ADO_Conn.htm and
    > http://www.connectionstrings.com/ .
    >
    > Once you will be able to connect to MSDE or to SQL-Server, you shouldn't
    > have any real problem. However, this is a setup that you must resolve by
    > yourself. A good book on MSDE or SQL-Server will not hurt here. Make
    > sure that the authorization mode is set to Mixed (Window and SQL-Server
    > login) and not to Window only because you home machine is not part of your
    > college domain.
    >
    > Using an Access MDB file with linked tables is the easiest way and can be
    > done very quickly. There is an Upsizing wizard (upsizing means to move
    > the data tables from Access to SQL-Server) that will do this for you. All
    > you will have to do after will be to add the parameter dbSeeChanges for
    > some .Execute and OpenRowSet commands is you are using DAO instead of ADO.
    > For example:
    >
    > Dim db As DAO.Database
    > Set db = CurrentDb
    >
    > Dim rs As DAO.Recordset
    > Set rs = db.OpenRecordset("dbo_tblCustomer", dbOpenDynaset,
    > dbSeeChanges)
    >
    > Each time that you will forget to set this parameter, Access will tell
    > you; so it will be pretty easy to find all the relevant places.
    >
    > The only problem you may have is a performance problem when joining linked
    > tables; as this involve a lot of network communication. However, a subtle
    > use of views here and there can alleviate most of these problems. Here an
    > article about setting a view into an updatable view under Access:
    > http://support.microsoft.com/kb/q209123/
    >
    > With some testings; you shouldn't have any problem.
    >
    > You can also use ADP but it's a more difficult topic and nothing forbid
    > you to try it as a second phase to your project; i.e. you can use both MDB
    > and ADP in the same time as frontends to your database.
    >
    > S. L.
    >
    > "John Barnes" <JohnBarnes@discussions.microsoft.com> wrote in message
    > news:8F00CDA4-B2D6-42D1-8ED7-B56FA125A2E0@microsoft.com...
    >> Sylvain,
    >>
    >> Thanks for your responses so far. I'm still confused about how to
    >> proceed.
    >> A bit of background:
    >> I have a small department (3 employees) who will work from several sites
    >> in
    >> Northeast Ohio. Each user has broadband connnection. We will never
    >> expand
    >> beyond this amount in the forseable future. Rarely will users be
    >> accessing
    >> the database at the same time due to our schedules. Users each need to
    >> enter
    >> client data (meeting times, notes, etc) which others need to be able to
    >> view,
    >> run reports on, etc.
    >>
    >> I have internet access through a county wide Sparcc server through the
    >> school building I work in. My agency has a website which supports ASP.
    >>
    >> I have read various posts about splitting database and using MSDE for the
    >> backend. Here you mentioned ASP.
    >>
    >> I have tried MSDE, but haven't been successful yet. Our MIS person is
    >> working on switching my computer IP from a private to a public, which he
    >> says
    >> will be able to serve as SQL server.
    >>
    >> My questions is, which approach is best:
    >> 1. Do I set up my desktop computer to serve as SQL server, use MSDE and
    >> have
    >> users connect that way?
    >> 2. Do I use ASP and put database on the company server?
    >>
    >> When I created an ADP according to Access' online help, it didn't connect
    >> properly. When I installed it at home to test (dial up modem) the
    >> connection
    >> icon in the taskbar didn't even flicker as if computer was trying to
    >> access
    >> SQL server. Gave an error message about server unavailable.
    >>
    >> I am somewhat skilled in designing databases for local use, but Internet
    >> accessibility is certainly challenging. Thanks for your help.
    >>
    >> "Sylvain Lafontaine" wrote:
    >>
    >>> The easiest way might be to use ASP (older but simpler) or ASP.NET
    >>> (newer
    >>> and more complicated but much more powerfull).
    >>>
    >>> S. L.
    >>>
    >>
    >>
    >> "Sylvain Lafontaine" wrote:
    >>
    >>> The easiest way might be to use ASP (older but simpler) or ASP.NET
    >>> (newer
    >>> and more complicated but much more powerfull).
    >>>
    >>> S. L.
    >>>
    >>> "John Barnes" <JohnBarnes@discussions.microsoft.com> wrote in message
    >>> news:B835C239-FFCA-45F3-B5DA-740E8A9B4EDA@microsoft.com...
    >>> > Have read various posts and online help in Access, but I can't
    >>> > determine
    >>> > an
    >>> > easy way to put my Access 2003 database online.
    >>> >
    >>> > Where can I find information about how to place a database online?
    >>> >
    >>> > Thanks!
    >>>
    >>>
    >>>
    >
    >


  • Next message: DP: "Elementary help?"