Results 1 to 3 of 3
  1. #1
    2 Star Lounger
    Join Date
    Aug 2002
    Location
    Minneapolis, MN, Minnesota
    Posts
    162
    Thanks
    1
    Thanked 0 Times in 0 Posts

    Access Connectivity (2000)

    I would like to pose a couple of questions about
    Easy Access

  2. #2
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Access Connectivity (2000)

    I urge you to reconsider this design. Access is not designed to work properly in this scenario and your risk of corruption is very high. You would be better off considering replication of the backend and allowing the dialup users to simply connect and sync periodically. How do you see VPNs are improving the situation is those users still connect via dial up?
    Charlotte

  3. #3
    Super Moderator
    Join Date
    Aug 2001
    Location
    Evergreen, CO, USA
    Posts
    6,623
    Thanks
    3
    Thanked 60 Times in 60 Posts

    Re: Access Connectivity (2000)

    As Charlotte indicates, working with a database remotely is very dicey over dial-up connections. We've tried them and frankly never could see much corruption, because it was so slow we never even let our users try it out. Even with a laptop front-end, just to work with a table is painful - it has to pull the entire table across the connection because that's the way Jet works. It's a bit better if you have a SQL Server or MSDE back-end, as in many cases the work gets done on the server PC, and the amount of data transferred is much smaller, but still not really viable. Charlotte's suggestion of replication is one approach we've used, though the care and feeding of replicated databases can be a challenge - replication also causes a database to balloon in size by about 50%.

    The approach we use most often these days is using Windows Terminal Services - we actually work with databases 1000 or more miles away, and as long as you are on a DSL connection it is reasonably viable. That approach, much like pcAnyWhere from Symantec, simply sends screen updates to the remote laptop, and keystrokes and mouse clicks from the laptop. It's still pretty slow with dial-up speeds but if you can get 100Kbit connection or better, it's not bad. Not quite like being there, as the latentcy can be bothersome, but certainly viable.
    Wendell

Posting Permissions

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