Corrupted Access Database?

[Adigga1]

Hello everyone,
I have a completed MS Access database , it was created in Access 2003 cleared and operates in an Access 2007 environment.
The database was working great; entering data in forms, retrieving data, run reports, etc. All of a sudden, a user was handed the database now it has become very unstable and acting erratically.
When I fix this issue, how can I prevent this from happening or how to protect the database and codes from becoming unstable or tamper proof in the future?
I am using Access 2007.
Thanks in advance
A…

 

[llkhoutx]

Welcome to the world of Microsoft Access.

Repair and compact after changes. If Access won't let you repair and compact, create a blank database and import all object from 1st database into the blank database.

 

[Adigga1]

Welcome to the world of Microsoft Access.

Repair and compact after changes. If Access won't let you repair and compact, create a blank database and import all object from 1st database into the blank database.

Thank you for the reply, llkhoutx

Is there an option in Access 2007 that will allow me to repair and compact? If so, where do I navigate? And what measures can I take to safeguard against this moving forward?

Thank you again

A..

 

[RainLover]

Do you have a split Database?

 

[Adigga1]

Do you have a split Database?

No I do not: could that have been a problem

Thanks RainLover

A....

 

[Galaxiom]

Not splitting is definitely a problem.

 

[RainLover]

That is your problem. Almost guaranteed.

 

[gemma-the-husky]

not splitting becomes an issue in a multi-user database - for single user it doesnt matter

the point is, that the data should be shared between multiple users - but not the code

so you should not put the database on a server, but should give each user their own copy of the database - all linked to the backend on the server.

hence, splitting.

----------
note that when you split, a very small number of things may not work - eg access to tables using INDEXES and SEEK methods will now fail

 

[RainLover]

Dave

Perhaps I am splitting hairs here.

Isn't the Database the Backend where the Data is stored and the Front End is simply the GUI as it does not normally store data.

 

[Adigga1]

not splitting becomes an issue in a multi-user database - for single user it doesnt matter

the point is, that the data should be shared between multiple users - but not the code

so you should not put the database on a server, but should give each user their own copy of the database - all linked to the backend on the server.

hence, splitting.

----------
note that when you split, a very small number of things may not work - eg access to tables using INDEXES and SEEK methods will now fail

Thanks Dave for the input and suggestion.

But I may need a little coaching or description on how to accomplish this; I will also research these steps as well. But as it stands, it is a stand alone Access database. There is only one person accessing the database and entering data and adding records to it.

But she managed to screw up the dbase. What should do to remedy this and safeguard this from reocurring?

Thanks

A...

 

[RainLover]

<< become very unstable and acting erratically. >>

Based upon your last reply, I think it would be good to know what you mean by unstable and acting erratically.

You also used the word very. What do you class as very.