Alterations in Form Design Cause Crash

  • Thread starter Thread starter Tim Johnson
  • Start date Start date
T

Tim Johnson

Hi there,

I have recently deployed a database, and am having issues in that every time
a form is opened and altered in design mode, it causes some type of
corruption and requires redeployment. The error message gives no number and
just states that "There was an error executing the command". I have compiled
and compacted/repaired the database multiple times, but this is happening a
lot. I've also had this occur in other databases, for not apparent reason.
The situation doesn't seem to discriminate based upon whether a database is
split or not.

I've also tried repairing my Office program from the Add/Remove Software
area of the Control Panel, to no avail.

Is anyone aware of what might be causing this/how to prevent this from
happening; or any resources discussing this issue?

Thanks in advance,
Tim
 
At times like this, nothing beats a good backup. In fact make a complete
backup of your database now and put it away for safe keeping.

Tony Toews has an excellent web page on database corruption.
http://www.granite.ab.ca/access/corruptmdbs.htm

Allen Brown also has excellent info on corruption.
http://allenbrowne.com/ser-47.html

I have a white paper in a Word document named Fix Corrupt Access Database
towards the bottom this page:
http://www.rogersaccesslibrary.com/OtherLibraries.asp

If I had to make a guess, I'd look very carefully at the network especially
if the FE is out on the network and not on the user's PC.
 
Tim Johnson said:
I have recently deployed a database, and am having issues in that every time
a form is opened and altered in design mode, it causes some type of
corruption and requires redeployment. The error message gives no number and
just states that "There was an error executing the command".
Click to expand...

I have such problems occasionally myself for no good reason. Usually
it's been several hours since my last backup and all kinds of tedious
work has been done such as precisely aligning controls.

You could try the following if it works.

Corrupt Objects within a Corrupt Microsoft Access MDB
http://www.granite.ab.ca/access/corruption/corruptobjects.htm

The little documented SaveAsText and LoadFromText may help if an
object is corrupted or otherwise behaving weirdly.
At the debug/immediate window type:
Application.SaveAsText acForm,"MyForm","c:\form.txt
You can load the file into a new MDB.
Application.LoadFromText acForm,"MyForm","c:\from.txt"

Sample code at http://www.datastrat.com/Code/DocDatabase.txt for
saving all objects in an MDB.

Or import the object from your last backup.

BTW, this is a harsh lesson but I always make a backup every hour or
two of my FE database.

Making copies of your database during the working day
http://msmvps.com/blogs/access/arch...-of-your-database-during-the-working-day.aspx

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
 
Back
Top