Microsoft Access and Vista

  • Thread starter Thread starter Ashley Thomer
  • Start date Start date
A

Ashley Thomer

Does anyone know a fix around loosing your data when doing a compact and
repair in Microsoft Access on Vista? We have a quoting software, when they
select yes to optimize the database (compact and repair) it wipes their
entire database clean along with the backup copy on the desktop. Please
help...big problem!

Thanks
Ashley
 
Ashley Thomer said:
Does anyone know a fix around loosing your data when doing a compact and
repair in Microsoft Access on Vista? We have a quoting software, when
they select yes to optimize the database (compact and repair) it wipes
their entire database clean along with the backup copy on the desktop.
Please help...big problem!

Thanks
Ashley
You might want to try this question in the microsoft.public.access
newsgroup.
 
How about copying the Access file to another hard drive before trying to
compact and repair. It seems that your database has serious problems and
when the repair starts, wipes everything out.

Try creating a new database from scratch. Then rerun your your quoting
software and select the optimization on the new file. Does it give you the
same results? If it does, then look at the quoting software. If it doesn't
then you know the answer.
 
Does anyone know a fix around loosing your data when doing a compact and
repair in Microsoft Access on Vista? We have a quoting software, when
they select yes to optimize the database (compact and repair) it wipes
their entire database clean along with the backup copy on the desktop.
Please help...big problem!


I suggest you post to one of the access newsgroups under
microsoft.public.access. Here is a list of MS public newsgroups:
http://aumha.org/nntp.htm
 
I haven't tried copying it to another hard drive. I don't know that it is
the database having serious problems as i can create a fresh database with
only one estimate and it still wipes out everything.

thanks,
ashley
 
woller said:
Try taking the database off of the current computer and place it on
another to see if you get the same results. If the problem persists
only on the one computer it may not be a database issue at all.

Smooth move... you replied to a thread that died over a freaking YEAR
AGO.
 
Back
Top