dcsimg
CodeGuru Home VC++ / MFC / C++ .NET / C# Visual Basic VB Forums Developer.com
Results 1 to 15 of 28

Thread: Will Access database crash?

Hybrid View

  1. #1
    Join Date
    Sep 2004
    Posts
    292

    Will Access database crash?

    I'm having tensions with my access database as it has already grown to around 60mb, it records lots of pictures.The system I programmed automatically back-ups the database when it exits. It also compacts and repairs the database for any errors at startup and when exiting...

    I'm just wondering what are the tendencies that my database would crash (be corrupted or sort of...) and what maybe the possible factors that would cause the database from crashing....

    Please help.....

  2. #2
    Join Date
    Jul 2004
    Location
    Jakarta, Indonesia
    Posts
    596

    Re: Will Access database crash?

    see this Access Limitation

    just a suggestion..why don't u store the path to the picture rather than save all of it..

    1st NF - a table should not contain repeating groups.
    2nd NF - any fields that do not depend fully on the primary key should be moved to another table.
    3rd NF - there should be no dependency between non key fields in same table.
    - E. Petroutsos -


    eRiCk

    A collection of "Laku-abis" Ebook, Permanent Residence

    Access Reserved Words, a Classic Form Bug, Access Limitation, Know run Process and the Lock they hold in, Logging User Activity in MSSQL

  3. #3
    Join Date
    Oct 2003
    Location
    .NET2.0 / VS2005 Developer
    Posts
    7,104

    Re: Will Access database crash?

    i know of an access database concurrently used by 20+ users, and holds in excess of a million records. i shudder to think what filesize it is.. i know we have problems with ours when it grows to around 60mb. one of our competitors has a product based on access, and the stock database is 400mb. I'm impressed, especially with the speed of lookup; only a few seconds on a pentium 133 with 32mb of ram
    "it's a fax from your dog, Mr Dansworth. It looks like your cat" - Gary Larson...DW1: Data Walkthroughs 1.1...DW2: Data Walkthroughs 2.0...DDS: The DataSet Designer Surface...ANO: ADO.NET2 Orientation...DAN: Deeper ADO.NET...DNU...PQ

  4. #4
    Join Date
    Jul 2004
    Location
    Jakarta, Indonesia
    Posts
    596

    Re: Will Access database crash?

    cjard do u know by any chance what method that they used for lookup speed that u mention about?

    1st NF - a table should not contain repeating groups.
    2nd NF - any fields that do not depend fully on the primary key should be moved to another table.
    3rd NF - there should be no dependency between non key fields in same table.
    - E. Petroutsos -


    eRiCk

    A collection of "Laku-abis" Ebook, Permanent Residence

    Access Reserved Words, a Classic Form Bug, Access Limitation, Know run Process and the Lock they hold in, Logging User Activity in MSSQL

  5. #5
    Join Date
    Sep 2004
    Posts
    292

    Re: Will Access database crash?

    Am I right that converting a .bmp file to a .jpg file will have a reduction in filesize? Maybe I can convert those .bmp's to .jpg before saving them into the database. I'm also thinking of making a program that will transfer the data in my Access database into an SQL Server database, do you think it will take a lot of work in modifying my application which is employing DAO to connect to the Access database? By the way, can a DAO connect to an SQL Server? I'm a newbie to SQL Server.

  6. #6
    Join Date
    Aug 2003
    Location
    London
    Posts
    515

    Re: Will Access database crash?

    Converting to jpg or gif will reduce filesize, I think bmp is one of the largest file types.

    You should use ADO with the SQLOLEDB provider to connect to a SQL Server instance, DAO is tied in to Access Jet.OLEDB provider.

    Its takes a bit of time to convert your code but it's worth it!

  7. #7
    Join Date
    Oct 2003
    Location
    .NET2.0 / VS2005 Developer
    Posts
    7,104

    Post Re: Will Access database crash?

    Quote Originally Posted by erickwidya
    cjard do u know by any chance what method that they used for lookup speed that u mention about?
    putting everything interesting into one massively long but incredibly thin table with a very unique key, basically.. and that is linked to a very very large, detailed table..

    the lookup of the key is incredibly quick, and hence pulling the related row out of the huge table is easy. other products ive seen, by comparison, rely on several large tables, with indexes. searching these tables seems to take significant amounts of time, and the real criminal move is one where several huge tables are joined merely so that the product descriptions can be searched in one query..
    "it's a fax from your dog, Mr Dansworth. It looks like your cat" - Gary Larson...DW1: Data Walkthroughs 1.1...DW2: Data Walkthroughs 2.0...DDS: The DataSet Designer Surface...ANO: ADO.NET2 Orientation...DAN: Deeper ADO.NET...DNU...PQ

Posting Permissions

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


Windows Mobile Development Center


Click Here to Expand Forum to Full Width




On-Demand Webinars (sponsored)