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

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!

Replies are listed 'Best First'.
RE: RE: RE: Re: DBI module and MS Access
by Fastolfe (Vicar) on Oct 02, 2000 at 18:02 UTC
    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.
[reply]
      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!

[reply]
        Like I said, maybe it's just something unique with our setup. Most of our applications and drivers are homogenous (corporate standards/policies are not lenient as far as varying versions of software, even as far as limiting what service packs are installed).

        *shrug*

[reply]

In Section Seekers of Perl Wisdom