My business has been working with an Access database for 3 years without
incident until around 3 months ago when the following message started
appearing:

"The database has been converted from a prior version of Miscrosoft Office
Access by using the DAO Compactdatabase method instead of the Convert
database command on the toolbar and has left the database in a prtially
converted state"

I am the designer of the database we use. No one in my business has the
knowledge or experience to 'alter' or 'write' a command that would cause this
other than me.

We have a Microsoft Solution Partner who has been helping us with this
problem...including recently updating all the Access programs in our store to
the same version...but to no avail: we continue to have the problem (now
going on 3 or 4 months). The problem has happened about 10 times now and the
frequency is happening more often.

This 'problem' is causing us down time...let alone lost data...and we are
now in the habit of creating a copy every night - which is becoming
inconvenient as the person making the copy has to go around the store closing
the database on any other computer that has it open before a copy can be made.

Is this a known, documented problem? What should we look for that can be
causing this problem? We are desperate to find a cure.

Additional info: We are on a Microsoft server and a total of 5 computers run
Access...as has always been the case.






--
Anthony at Ashleighs

Do all the PCs that use the file have the same version of ACCESS? If not,
when one person closes file using a newer version, and if you have Compact
On Close option set to Yes, that may be the cause of this problem.
--

Ken Snell
<MS ACCESS MVP>




"Anthony" <(E-Mail Removed)> wrote in message
news:56123C9C-D5E3-4AF9-997C-(E-Mail Removed)...
> My business has been working with an Access database for 3 years without
> incident until around 3 months ago when the following message started
> appearing:
>
> "The database has been converted from a prior version of Miscrosoft Office
> Access by using the DAO Compactdatabase method instead of the Convert
> database command on the toolbar and has left the database in a prtially
> converted state"
>
> I am the designer of the database we use. No one in my business has the
> knowledge or experience to 'alter' or 'write' a command that would cause
> this
> other than me.
>
> We have a Microsoft Solution Partner who has been helping us with this
> problem...including recently updating all the Access programs in our store
> to
> the same version...but to no avail: we continue to have the problem (now
> going on 3 or 4 months). The problem has happened about 10 times now and
> the
> frequency is happening more often.
>
> This 'problem' is causing us down time...let alone lost data...and we are
> now in the habit of creating a copy every night - which is becoming
> inconvenient as the person making the copy has to go around the store
> closing
> the database on any other computer that has it open before a copy can be
> made.
>
> Is this a known, documented problem? What should we look for that can be
> causing this problem? We are desperate to find a cure.
>
> Additional info: We are on a Microsoft server and a total of 5 computers
> run
> Access...as has always been the case.
>
>
>
>
>
>
> --
> Anthony at Ashleighs