Results 1 to 6 of 6
  1. #1
    Join Date
    Jun 2008
    Posts
    163

    Unanswered: access-only networking over the internet

    My access db runs in a local area network (multiple front end mdbs accessing a single back end mdb via shared/network folders; well, just 3 computers accessing one).

    Security considerations aside, is there a way to open an mdb to internet sharing from within access (not counting mySQL and other programs)?

    I am considering migrating the database (at least the backend) into mySQL, but that's an eventual step that's pretty far down the road for me. I'm still learning access as it is.

  2. #2
    Join Date
    Nov 2007
    Location
    Adelaide, South Australia
    Posts
    4,049
    I'm not quite sure what you are asking... but if it is "can I just run an Access database from a web browser", the answer is no. You can look at Data Access Pages and such, but if you really want to run a database online, it should be developed in PHP or something like that.
    Owner and Manager of
    CypherBYTE, Microsoft Access Development Specialists.
    Microsoft Access MCP.
    And all around nice guy!


    "Heck it's something understood by accountants ... so it can't be 'that' difficult..." -- Healdem
    "...teach a man to code and he'll be frustrated for life! " -- georgev

  3. #3
    Join Date
    Nov 2004
    Location
    out on a limb
    Posts
    13,692
    Provided Answers: 59
    there is no reason why you cannot deploy an access database over the internet for remote use....
    make sure that people usng he app have a local copy of the mdb (let them down load the app)
    except that it would be horrendously slow, prone to collapse and probably have masses of data problems,you wouldn't be able to support many users, unless you have used the unbound forms design approach

    The problem is how JET handles data.. its a file server model. the client requests the data, JET sends the indexes and the data so there is a heck f a lot of network traffic for the client to decide what data it needs. that will clog your internet connection (it one of the reasons why many 'professional' developers sneer at Access becuase its a network bandwidth hog. using a server back end removes that bottleneck but many 'profesionals' either don't know that or choose to ignore it. but yu hvae to design for using a server back end from the ground up.. that means NOT using bound forms but unbound forms, it means not using any VBA in queries, i tmenas using none of the whizzy bits of Access, and very very carefull design of any bit using data (always use pass through queries). but if you do consider going down that route then I'd stronlgy reccomend you get the sybex developer book suggested earlier
    I'd rather be riding on the Tiger 800 or the Norton

  4. #4
    Join Date
    Jun 2008
    Posts
    163
    make sure that people usng he app have a local copy of the mdb (let them down load the app)
    Thanks for the answers!

    Slowdown is fine for me, and the intended front end to be used for accessing the db is on a view-only setting (no edits, no adds, no deletes).

    I am weighing the amount of work to do if it's done entirely within the abilities of access as compared to using an sql server. Seems like a migration would be a wiser move.

    Are there any good references for learning how to create unbound forms?
    Last edited by coffeecat; 08-13-08 at 21:34.

  5. #5
    Join Date
    Nov 2004
    Location
    out on a limb
    Posts
    13,692
    Provided Answers: 59
    yeah sybex developers handbook for the version of Access you are using

    and Im sure there are lots of references on t'net
    I'd rather be riding on the Tiger 800 or the Norton

  6. #6
    Join Date
    May 2003
    Location
    Dallas
    Posts
    817
    Provided Answers: 5
    If you are going to use backend tables you will have to do one of two things -
    VPN - which can be slow unless you use dedicated routers (i.e Sonic Wall brand ) or use remote access (terminal services ) and load the sessions from a computer at the dat alocation - which is what I have running on a clients business where in houston - 15 stores using Terminal Services and running the MDE not from there PC but from the server at the corprorate office - Not much lag and very cost effective.

    Also if using multi-site access apps - I like upsizing the table to runtime SQL and then using DSN-Less connection string on start up to avoid performance hits using a local dsn file.

    I hope this helps - and Data Access pages aren't bad either - at least for retrieving and viewing data.
    Dale Houston, TX

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •