in reply to Re: DBI module and MS Access
in thread DBI module and MS Access

Access isn't quite that bleak but you aren't far off:P I think the hardest I have pushed a .mdb is 80 megs. Generating rollup reports for an 80 meg DB took about 15 minutes:P Although, at 10 megs it ate the reports for lunch. Keep in mind, I was never interfacing with the DB through the MSAccess application. I bet MS Access is not happy trying to refresh screens *shudder*.
Access can also handle a fair number of connections at once. I can guess that I have had somewhere between 10 - 20 people on at once. I don't think I would trust it with much more though.
I love your point about garbage! The first time I learned about that I was wondering where all my drive space was going when someone asked me when the last time I compacted my DB was.

Replies are listed 'Best First'.
RE: RE: Re: DBI module and MS Access
by puck (Scribe) on Oct 02, 2000 at 01:33 UTC
    Uh oh...

    You use MS Access as a multi user DB? Have much trouble with data loss? It's a cool program for single user DB's, but I wouldn't trust it multiuser... Actually, it's possible that if you only use ODBC to access it things will be okay, but I've seen people share the MDB on a network drive and have multiple people opening the file. This is a good way to corrupt your database.

    Cheers!

      Note that I don't care for MS Access either (most of my work is done with Oracle on Unix), but we have a relatively medium (20-30MB, which is nothing compared to what we do under Oracle) Access database shared that 30-50 people routinely enter, update and pull reports from. I don't think we've ever had an issue with data corruption... Maybe we were using a more stable version of the software or something, or maybe network problems corrupted your database... strange.
        Wow... Groovey...

        I've just checked the MS Knowledge base and you can have data loss, silent design changes to orms, reports, macros, modules, or commandbars, may be discarded without warning. Check out article Q237938 for more details.

        But I have heard of other problems as well, although this was a couple of years ago with Access 95 which have probably been cleaned up by now. Or at least, I'd hope so!