Welcome to SPN

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

Sign Up Now!

Split/Upload etc

Discussion in 'Information Technology' started by Lin, Nov 5, 2005.

  1. Lin

    Lin
    Expand Collapse
    Guest

    Hi all, thanks in advance

    I am a little confused. I have read much but understand little. I have
    created a database and want to place on the server at work, or use my own PC
    as the server, having said that, some queries are quite slow, but relatively
    effective based on 250,000 or so files. It was explained that I should
    upload to an SQL server.
    a couple of questions then...

    Do I split the database first and then upload the back end?
    Do I upload and then split?

    Regards....
     
  2. Loading...


  3. John Vinson

    John Vinson
    Expand Collapse
    Guest

    On Fri, 4 Nov 2005 17:28:00 -0800, Lin <Lin@discussions.microsoft.com>
    wrote:

    >Hi all, thanks in advance
    >
    >I am a little confused. I have read much but understand little. I have
    >created a database and want to place on the server at work, or use my own PC
    >as the server, having said that, some queries are quite slow, but relatively
    >effective based on 250,000 or so files. It was explained that I should
    >upload to an SQL server.


    250,000 "files"? Do you mean records in a table? Access doesn't use
    "files".

    The first thing to check (whether the database is in JET .mdb file or
    in SQL/Server) is that you have the appropriate indexes defined. Any
    field used as a Primary Key or as a linking field in a defined
    relationship will already have an index; but you may need to add
    indexes to those fields used for search criteria or for sorting.

    Access should be able to handle tables of this size pretty nicely,
    though if you have SQL installed, it may well be worth the
    (considerable) effort of upgrading.

    >a couple of questions then...
    >
    >Do I split the database first and then upload the back end?
    >Do I upload and then split?


    Split, then upload the backend; then use Tools... Database
    Utilities... Linked Table Manager in the frontend to point the
    frontend links to the relocated backend.

    John W. Vinson[MVP]
     
  4. Albert D.Kallal

    Albert D.Kallal
    Expand Collapse
    Guest

    The idea of splitting is simply a idea in which you want to turn the results
    into two parts:

    data part
    application/program part.

    So, the goal here is to make a data only file, and remove any forms,
    queries, code etc.

    It is this data only part you put on the shared folder..

    I explain in detail about this here:
    http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm

    --
    Albert D. Kallal (Access MVP)
    Edmonton, Alberta Canada
    pleaseNOOSpamKallal@msn.com
    http://www.members.shaw.ca/AlbertKallal
     
  5. Lin

    Lin
    Expand Collapse
    Guest

    Hello John and Albert thank you both.

    We were using a flat file for a few years. This is shared over the network.
    The company wants
    to replace this older one with the new one. Is it necessary to even bother
    splitting the db. I should note that I am using a list box to search,
    similar to Arvin Meyers example, however I had to build a query first to join
    Surnames to a table (related).

    This can double and triple in some cases how big this thing is. Hence the
    slow query. As I mentioned earlier I m not quite sure if it needs to be
    uploaded to an SQL. I understand the split DB concept and so on but what
    confuses me is that

    If I split the DB, it renames the file,
    When I do the upload to SQL (If i understand corectly, this also renames the
    DB)
    If this is correct, I am guessing that I then have to relink everything.
    Also, It seems to SQL tables only, what about the query, or is it just based
    on the relationship aspects?

    Sorry for all this, I have done small stuff, but nothing like this. Even a
    suggested book in simple terms would be helpful.

    Sincerest regards

    LS

    "Lin" wrote:

    > Hi all, thanks in advance
    >
    > I am a little confused. I have read much but understand little. I have
    > created a database and want to place on the server at work, or use my own PC
    > as the server, having said that, some queries are quite slow, but relatively
    > effective based on 250,000 or so files. It was explained that I should
    > upload to an SQL server.
    > a couple of questions then...
    >
    > Do I split the database first and then upload the back end?
    > Do I upload and then split?
    >
    > Regards....
     

Share This Page