Welcome to SPN

Register and Join the most happening forum of Sikh community & intellectuals from around the world.

Sign Up Now!

Access as back-end for web app

Discussion in 'Information Technology' started by cjb3@hotmail.com, Jul 28, 2006.

  1. cjb3@hotmail.com

    cjb3@hotmail.com
    Expand Collapse
    Guest

    Looking for sound advice. I'd abondoned Access for the last few years
    and have worked almost exclusively on web applications using asp.net
    and sql server. However, an interesting project has come along and
    I'm wondering if Access may actually be a better web back-end solution
    for it.

    1 - data security is of top importance.
    2 - The database will only have 1 or 2 concurrent users
    3 - Users must be able to work off-line (read/update) and on-line from
    any loc

    The solution I am thinking of involves:

    1 - Build an Access back-end and Access front-end for the client pc
    2 - Copy Access back-end to use on web server
    3 - Build asp.net interface for on-line access (when user doesn't have
    own pc)
    4 - Build "publish" feature to overwrite web db when user updates
    locally
    5 - Provide option for user to work on own pc, but connected to web db

    My goal is provide the same flexibility as a client program for
    off-line use while providing web read/write access to data. Given
    that it's only 1 or 2 users with data no more than 1GB, wouldn't an
    Access back-end on the web be sufficient? Even so, I would normally
    use sql server anyway, except that in this case -- and here's the catch
    --- there will ultimately be other users of the same app, but it's
    important that their data NOT be contained in the same db (because it
    may need to be hosted elsewhere). I'm assuming it's not as
    cost-effective to copy a sql db for each prospective user.

    Are there sure-fire ways to overwrite the mdb file on the web server
    (e.g., if something is left "open")?

    Thanks,
    CBRUNO
     
  2. Loading...


  3. Arvin Meyer [MVP]

    Arvin Meyer [MVP]
    Expand Collapse
    Guest

    Your scenario would work fine. I have one similar to it in place but for
    about 10 or 11 users. If you could guarantee only one or two concurrent
    users, Terminal Services would be a far easier (and cheaper) answer. Then
    you could solve all your requirements with the same Access application and
    wouldn't need to invest in the time to write the asp app.

    --
    Arvin Meyer, MCP, MVP
    Microsoft Access
    Free Access downloads
    http://www.datastrat.com
    http://www.mvps.org/access

    <cjb3@hotmail.com> wrote in message
    news:1148169009.852905.223440@j55g2000cwa.googlegroups.com...
    > Looking for sound advice. I'd abondoned Access for the last few years
    > and have worked almost exclusively on web applications using asp.net
    > and sql server. However, an interesting project has come along and
    > I'm wondering if Access may actually be a better web back-end solution
    > for it.
    >
    > 1 - data security is of top importance.
    > 2 - The database will only have 1 or 2 concurrent users
    > 3 - Users must be able to work off-line (read/update) and on-line from
    > any loc
    >
    > The solution I am thinking of involves:
    >
    > 1 - Build an Access back-end and Access front-end for the client pc
    > 2 - Copy Access back-end to use on web server
    > 3 - Build asp.net interface for on-line access (when user doesn't have
    > own pc)
    > 4 - Build "publish" feature to overwrite web db when user updates
    > locally
    > 5 - Provide option for user to work on own pc, but connected to web db
    >
    > My goal is provide the same flexibility as a client program for
    > off-line use while providing web read/write access to data. Given
    > that it's only 1 or 2 users with data no more than 1GB, wouldn't an
    > Access back-end on the web be sufficient? Even so, I would normally
    > use sql server anyway, except that in this case -- and here's the catch
    > --- there will ultimately be other users of the same app, but it's
    > important that their data NOT be contained in the same db (because it
    > may need to be hosted elsewhere). I'm assuming it's not as
    > cost-effective to copy a sql db for each prospective user.
    >
    > Are there sure-fire ways to overwrite the mdb file on the web server
    > (e.g., if something is left "open")?
    >
    > Thanks,
    > CBRUNO
    >
     

Share This Page