Recent content by villaw

  1. V

    LArge Table Split

    yes I am using UNC paths and the connection is a hardware 100mb even though I have never checked the real bandwidth. I see where this is going and I will pay a lot more attention to the network. Never realised that this is so critical in this scenario.
  2. V

    LArge Table Split

    thank you for your time this is a LAN connection. Each desktop user has the front end in his drive which in turn accesses the back end db via linked table. ie one front end per user locally and one back end for everyone on the file server. Probably I am overly cautious but this is an...
  3. V

    LArge Table Split

    each user has his own front end installed on him desktop which in turn links to one backend. A true client server environment but I do sense limitations on the backend due to size. I have considered slipping the db into two but one table is the real backbone of it all and covers 2/3 of the whole...
  4. V

    LArge Table Split

    thank you very much for your prompt reply. Yes 50mb is not a lot (remember I am referring to the table in question not the mdb). I do regular compact/repair exercises but I have noticed that the bigger the table gets, the more frequent the corruptions (geometrically), hence my request...
  5. V

    LArge Table Split

    Hi all I have an ms access table which is the backbone of a an office invoicer/ management database and has grown quite a bit ie 50mb (the table alone). Is there any chance to split this table in two smaller ones or shall I just export it into an sql database and be done with it. My mdb is...
Back
Top Bottom