Corruption in Access 2k3 databases

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Jack Black - 05 Feb 2007 01:15 GMT

I seem to notice that Access 2k3 tables tend to get corrupted rather easily
when running as a database back-end for ASP applications (different
providers, different code, same structure and content corruption).

Are there any general practices that can prevent this corruption? I don't
have server access at the providers to install MDAC updates and such, so
what's the average developer with public websites to do?

Thanks!
Jack

Reply to this Message

Mike Brind - 05 Feb 2007 08:10 GMT

>I seem to notice that Access 2k3 tables tend to get corrupted rather easily
>when running as a database back-end for ASP applications (different
[quoted text clipped - 3 lines]
> don't have server access at the providers to install MDAC updates and
> such, so what's the average developer with public websites to do?

Use Sql Server 2005 Express Edition instead. If your current host doesn't
support it, there are plenty around that do.

You can delay the inevitable [corruption in Access] somewhat by following
the advice given here: http://support.microsoft.com/default.aspx/kb/303528

However, if your database is primarily there to serve up data, and not
perform UPDATES or INSERTS, you may find that an Access database will go for
years trouble-free.

--
Mike Brind

Reply to this Message

Mark J. McGinty - 05 Feb 2007 18:50 GMT

>I seem to notice that Access 2k3 tables tend to get corrupted rather easily
>when running as a database back-end for ASP applications (different
>providers, different code, same structure and content corruption).
>
> Are there any general practices that can prevent this corruption?

Basically, just one: don't use Access/Jet.

-Mark

> I don't have server access at the providers to install MDAC updates and
> such, so what's the average developer with public websites to do?
>
> Thanks!
> Jack

Reply to this Message

Webmaster Forum / ASP / Database Access / February 2007

Corruption in Access 2k3 databases