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

"Jack Black" <jackisback [at] hotmail.com> wrote in message
news:u$7isMMSHHA.1600 [at] TK2MSFTNGP05.phx.gbl...
>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?
>

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

"Jack Black" <jackisback [at] hotmail.com> wrote in message
news:u$7isMMSHHA.1600 [at] TK2MSFTNGP05.phx.gbl...
>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
>