only maybe.
If you split your database, the likelyhood of data corruption is reduced.
In my experience, it is ususally the front end or application that becomes
corrupt. The data or backend becoming corrupt is more rare.
You can try a compact and repair and see how that works.
You can try using the TransferDatabase from a new mdb and see if you get
your data.
But, ulimately, there is nothing like regular backups to protect you.
--
Dave Hargis, Microsoft Access MVP


"DS" wrote:

> If your Acess Database becomes corrupt for whatever reason. Is there a
> way to still access the info in the tables. Also I thought of backing
> up my access tables as CSV files is this wise? Is it a good idea? My
> database will be split as well.
> Thanks
> DS
>

If your Acess Database becomes corrupt for whatever reason. Is there a
way to still access the info in the tables. Also I thought of backing
up my access tables as CSV files is this wise? Is it a good idea? My
database will be split as well.
Thanks
DS

I don't see any real value. Backups are still be best bet.
--
Dave Hargis, Microsoft Access MVP


"DS" wrote:

> Klatuu wrote:
> > only maybe.
> > If you split your database, the likelyhood of data corruption is reduced.
> > In my experience, it is ususally the front end or application that becomes
> > corrupt. The data or backend becoming corrupt is more rare.
> > You can try a compact and repair and see how that works.
> > You can try using the TransferDatabase from a new mdb and see if you get
> > your data.
> > But, ulimately, there is nothing like regular backups to protect you.
> True backups are good. ButI was just wondering.
>
> BTW how about the CSV files? Is that a good idea or not?
> Thanks
> DS
>

Klatuu wrote:
> only maybe.
> If you split your database, the likelyhood of data corruption is reduced.
> In my experience, it is ususally the front end or application that becomes
> corrupt. The data or backend becoming corrupt is more rare.
> You can try a compact and repair and see how that works.
> You can try using the TransferDatabase from a new mdb and see if you get
> your data.
> But, ulimately, there is nothing like regular backups to protect you.
True backups are good. ButI was just wondering.

BTW how about the CSV files? Is that a good idea or not?
Thanks
DS

On Thu, 06 Sep 2007 17:10:07 -0500, DS <(E-Mail Removed)> wrote:

>BTW how about the CSV files? Is that a good idea or not?

It's a lot of extra work to get something that's no better than a good,
verified backup of the backend database.

John W. Vinson [MVP]

John W. Vinson wrote:

> On Thu, 06 Sep 2007 17:10:07 -0500, DS <(E-Mail Removed)> wrote:
>
>
>>BTW how about the CSV files? Is that a good idea or not?
>
>
> It's a lot of extra work to get something that's no better than a good,
> verified backup of the backend database.
>
> John W. Vinson [MVP]
OK, point taken. I was also wondering about the different types of
back-up. For instance, instead of backing up,or copying the whole
Database can I just copy the records from the tables in one database
into another? This way I wouldn't need to close the database. Also is
it better to compact and repair then backup or...backup and the compact
and repair?
Thanks
DS

Klatuu wrote:

> I don't see any real value. Backups are still be best bet.
I just thought that I would have the data in an easy to read basic
format so that if all else fails, key input could be used.
DS