Results 1 to 6 of 6
  1. #1
    Join Date
    Apr 2004
    Posts
    110

    Unanswered: new database project

    Hello everybody

    We need to build this more or less small database system that needs to work on several laptops that will be out on field work. After that we would like to be able to import that data on a central Access database. My initial question is whether Access can support such a scheme so that we can further pursue it`s implementation

    thanks, in advance

    George Papadopoulos

  2. #2
    Join Date
    Nov 2004
    Location
    out on a limb
    Posts
    13,692
    Provided Answers: 59
    Access can handle that perfectly happily
    the potential pitfalls are going to be
    how do you synchronise data between remote computers, you may need to use GUID's as PK's rather than autonumber columns. you may be able to get away with say a autonumber column and machineID
    if you want your remote laptops to use the same live data set then using the default database to store the data (JET) may be a problem, you may well be better off using a server backend to support the access front end.
    I'd rather be riding on the Tiger 800 or the Norton

  3. #3
    Join Date
    Oct 2009
    Posts
    340
    replication is the database term that you are requiring. It is a feature in Access in all the versions using .mdb file formats (2000-2003). It has been dropped from Access in Access2007 .accdb format - though 07 does support the .mdb format. And therefore one presumes going forward it will no longer be a feature. Thus you are at a development cross roads point in time so to speak....

    if you are in the .mdb format - then you implement the Replication feature. It is important that you get an Access textbook in the version you are using - read, and follow the instructions of replication closely. These books are widely available in big bookstores and on Amazon.

    one presumes the reason for MS to drop replication is that they view that web based solutions would be the growing alternative - - but this is just a guess. b.t.w. AccessTables.com - Home offers an alternative service approach that may work for you. They replicate tables for WAN/distributed Access applications.

  4. #4
    Join Date
    Feb 2004
    Location
    One Flump in One Place
    Posts
    14,912
    <OT> I would be surprised if that is the reason. Replication still features pretty heavily in SQL Server. In fact, there were quite a few questions about it in the SQL Server 2005 DBA exam.</OT>
    Testimonial:
    pootle flump
    ur codings are working excelent.

  5. #5
    Join Date
    Dec 2004
    Location
    Madison, WI
    Posts
    3,926
    Quote Originally Posted by NTC View Post
    replication is the database term that you are requiring. It is a feature in Access in all the versions using .mdb file formats (2000-2003). It has been dropped from Access in Access2007 .accdb format - though 07 does support the .mdb format. And therefore one presumes going forward it will no longer be a feature. Thus you are at a development cross roads point in time so to speak....

    if you are in the .mdb format - then you implement the Replication feature. It is important that you get an Access textbook in the version you are using - read, and follow the instructions of replication closely. These books are widely available in big bookstores and on Amazon.

    one presumes the reason for MS to drop replication is that they view that web based solutions would be the growing alternative - - but this is just a guess. b.t.w. AccessTables.com - Home offers an alternative service approach that may work for you. They replicate tables for WAN/distributed Access applications.
    Stay COMPLETELY AWAY from replication!!! It is absolutely horrible and will cause you NOTHING but HEADACHES!! - (take it from someone who has utilized replication in several projects.) Avoid it at ALL COSTS!! I'm serious!

    I would NEVER, NEVER, NEVER recommend Replication for anything! I won't list the dozens of problems (search for previous Replication posts in this forum).

    Your much better off:
    1. Having your laptop users connect via Citrix/Terminal Server/VPN/Remote Desktop to a network where the mdb is located (preferable)
    2. Designing an import/export routine in your MSAccess project and have users run these routines to transfer data (last case.)
    Last edited by pkstormy; 11-16-09 at 22:18.
    Expert Database Programming
    MSAccess since 1.0, SQL Server since 6.5, Visual Basic (5.0, 6.0)

  6. #6
    Join Date
    Oct 2009
    Posts
    340
    ok weeellllll.... so - the correct generic DB terminology for the requirement is replication.

    Now PK has a strong negative experience with Microsoft's product implementation of this task - ok noted.

    PF noted that replication is in use widely in sqlserver. Which is true. My comment/guess that Access dropped replication in assumption that users would go web based wasn't fully explained. Replication is a huge area that will always exist as long as there are distributed databases. And it exists with the high end DBs big time within the realm of data warehousing.

    So that is that. In the end - if one has a geographically distributed requirement for Access. One can use the AccessTables.com service or one can move it to a web architecture. If one is locally situated, though not on the same LAN - and can physically put them on the same LAN at least temporarily - - then one is able to use the embedded replication feature of the product (pre-07.accdb format)....but noting PK's opinion of this feature.

    Am not trying to push it one way or the other - just trying to lay out the options available.

Posting Permissions

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