Results 1 to 4 of 4
  1. #1
    Gold Lounger
    Join Date
    Jan 2004
    Location
    Italy
    Posts
    3,245
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Dubt...
    I use a conn with ADO and Access db.
    When the db is in c:\ all work fast.
    But if i save the db on server all work very slow.

    Now a friend suggest me to split db and copy one db on c:\ for all user tath use the application in vb and save the other copy in a dir of server.

    This operation permit the user to work on local and when the conn is close all dta from c:\ update the database in sever dir...

    or not?

    Or, save the same copy of db one in c:\ and one in server dir and link the 2 table and this operation permit the user to work on local and when the conn is close all dta from c:\ update the database in sever dir...

  2. #2
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts
    You could use replication to synchronize local and server copies of the database, but that's not an easy subject. Make sure you study the documents carefully before starting on it: Database Replication.

  3. #3
    5 Star Lounger AndrewKKWalker's Avatar
    Join Date
    Apr 2001
    Location
    Cambridge, UK
    Posts
    1,020
    Thanks
    0
    Thanked 3 Times in 3 Posts
    [quote name='sal21' post='799776' date='25-Oct-2009 10:25']Dubt...
    I use a conn with ADO and Access db.
    When the db is in c:\ all work fast.
    But if i save the db on server all work very slow.

    Now a friend suggest me to split db and copy one db on c:\ for all user tath use the application in vb and save the other copy in a dir of server.

    This operation permit the user to work on local and when the conn is close all dta from c:\ update the database in sever dir...

    or not?

    Or, save the same copy of db one in c:\ and one in server dir and link the 2 table and this operation permit the user to work on local and when the conn is close all dta from c:\ update the database in sever dir...[/quote]

    I had a similar issue, with an Access Front End and Back End.
    Just the tables on the Server and the rest on the Local Drive.
    It works well until the Data file gets large when we had performance issues.

    This may not be viable for you, but we moved the data layer to MYSQL, and linked the local Front End to the MYSQL Tables.
    There are a few conversion issues if there is a lot of VBA behind the forms,
    and you need to let the MYSQL Administrator convert the tables and change a few bits, but the performance increase was for us huge.
    Faster than if we used SQL Server as the back end.

    Since the tables are all linked you can use DAO or ADO code against them.
    You can also run server side procedures although MYSQL is no where near as refined as SQL Server yet,
    but it is free.

    Bit of work involved though if you went down this route.
    Andrew

  4. #4
    Super Moderator
    Join Date
    Aug 2001
    Location
    Evergreen, CO, USA
    Posts
    6,624
    Thanks
    3
    Thanked 60 Times in 60 Posts
    I've had a fair bit of experience with replication, and tend to view it as a last resort. The maintenance headaches associated with it can be substantial, and the fact that it is not supported in the latest ACCDB format make me reluctant to recommend it. SQL Server replication is more robust, so that might be an alternative to consider, but it has it's own set of complexities. Another alternative to look at is using remote execution software - examples are Remote Desktop as supported in Windows XP and Vista, or a product such as PCAnywhere, GoToMyPC, or LogMeIn. Access is slow in WAN situations because it generally pulls across entire tables in order to run queries.
    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
  •