I am working on an Access 2003 database. In the last 2 days I've had
Access corrupt 2 forms rendering them unloadable. (I would get the not
enough memory error message.) I had to scrap the one form entirely
since I had not backed up the database since creating the form. (Lots
of saves, but that doesn't help.) Fortunately, I had backed up the
database before doing some heavy edits to the form. I used the export
feature to copy the working form into the current database file.

I set up a VM on my XP machine so I could install the Office 2003
software and not worry about any conflicts with my Office 2007. Are
there any known issues with Microsoft Virtual PC and Access 2003? Are
there other issues I should investigate to prevent this from happening
in the future? The "Compact and Repair" feature in 2003 seems useless.
Are there other methods for fixing a corrupted form?

Thanks for any comments.
THANKS!
David G.

On Tue, 22 Jun 2010 20:58:15 -0400, David G. <(E-Mail Removed)>
wrote:

I get this occasionally as well.

> I set up a VM on my XP machine so I could install the Office 2003
>software and not worry about any conflicts with my Office 2007. Are
>there any known issues with Microsoft Virtual PC and Access 2003?

No.

>Are
>there other issues I should investigate to prevent this from happening
>in the future?

Not tthat I'm aware of.

>The "Compact and Repair" feature in 2003 seems useless.

In the case of objects other than tables, indexes and relationships
you are correct. To fix the other objects you must either copy and
paste from the database container window or import all the objects
into a new database file.

Corrupt Objects within a Corrupt Microsoft Access MDB
http://www.granite.ab.ca/access/corr...uptobjects.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.

Tony

On Tue, 22 Jun 2010 22:28:31 -0400, "Arvin Meyer" <(E-Mail Removed)>
wrote:

>I am running Office 2003 on VMWare on one machine without problems. Do you
>have SP1 and SP2 installed as well?

Good point but Office 2003 is up to SP3.

Tony

Thank you for your comments! I might go back to one of the corrupted
files and see if I can extract the corrupted form.
On Tue, 22 Jun 2010 20:29:42 -0600, Tony Toews
<(E-Mail Removed)> wrote:

>On Tue, 22 Jun 2010 20:58:15 -0400, David G. <(E-Mail Removed)>
>wrote:
>
>I get this occasionally as well.
>
>> I set up a VM on my XP machine so I could install the Office 2003
>>software and not worry about any conflicts with my Office 2007. Are
>>there any known issues with Microsoft Virtual PC and Access 2003?
>
>No.
>
>>Are
>>there other issues I should investigate to prevent this from happening
>>in the future?
>
>Not tthat I'm aware of.
>
>>The "Compact and Repair" feature in 2003 seems useless.
>
>In the case of objects other than tables, indexes and relationships
>you are correct. To fix the other objects you must either copy and
>paste from the database container window or import all the objects
>into a new database file.
>
>Corrupt Objects within a Corrupt Microsoft Access MDB
>http://www.granite.ab.ca/access/corr...uptobjects.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.
>
>Tony
THANKS!
David G.

I keep XP up to date. I tried to install Office SP3, but I got a
message saying it was already installed. I know I installed the
updates previously, but I had assumed reinstalling from the original
disc would have taken me back to square one. Perhaps the installation
process does not overwrite any newer version files?

Is there a way to uninstall the updates, or reinstall them?
On Tue, 22 Jun 2010 23:20:05 -0600, Tony Toews
<(E-Mail Removed)> wrote:

>On Tue, 22 Jun 2010 22:28:31 -0400, "Arvin Meyer" <(E-Mail Removed)>
>wrote:
>
>>I am running Office 2003 on VMWare on one machine without problems. Do you
>>have SP1 and SP2 installed as well?
>
>Good point but Office 2003 is up to SP3.
>
>Tony
THANKS!
David G.

On Wed, 23 Jun 2010 09:48:39 -0400, David G. <(E-Mail Removed)>
wrote:

>I keep XP up to date. I tried to install Office SP3, but I got a
>message saying it was already installed. I know I installed the
>updates previously, but I had assumed reinstalling from the original
>disc would have taken me back to square one. Perhaps the installation
>process does not overwrite any newer version files?
>
>Is there a way to uninstall the updates, or reinstall them?

Likely from within the Control Panel >> Add/Remove softeare but
you'll have to click that checkbox to show the patches. Be prepared
to wait a while for it to update the screen.

Tony

David G. <(E-Mail Removed)> wrote in
news:(E-Mail Removed):

> I am working on an Access 2003 database. In the last 2 days I've
> had Access corrupt 2 forms rendering them unloadable.

Are you practicing good code management?

That is:

1. turn off COMPILE ON DEMAND.

2. use Option Explicit in all modules.

3. specify the parents of all objects used (Me!MyFormControl and not
MyFormControl).

4. compile often (after every few lines of code).

5. decompile on a semi-regular basis (after a few hours of work,
before a release to production).

These kinds of daily practices generally reduce the occurence of
corruption to almost never.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

David G. <(E-Mail Removed)> wrote in
news:(E-Mail Removed):

> I know I installed the
> updates previously, but I had assumed reinstalling from the
> original disc would have taken me back to square one. Perhaps the
> installation process does not overwrite any newer version files

No, it does not. That was one of the main points in creating the
MSI, to manage this kind of thing. To revert to the earlier version,
you have to uninstall and reinstall from the source disks.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

On 23 Jun 2010 22:59:42 GMT, "David W. Fenton"
<(E-Mail Removed)> wrote:

>3. specify the parents of all objects used (Me!MyFormControl and not
>MyFormControl).

I use Me. Haven't yet had a problem with that.

Tony

Tony Toews <(E-Mail Removed)> wrote in
news:(E-Mail Removed):

> On 23 Jun 2010 22:59:42 GMT, "David W. Fenton"
><(E-Mail Removed)> wrote:
>
>>3. specify the parents of all objects used (Me!MyFormControl and
>>not MyFormControl).
>
> I use Me. Haven't yet had a problem with that.

I see a lot of code that doesn't specify parent objects, though. It
requires VBA to do more work, as well as causing the *programmer* to
do more work ("is MyFormControl a variable or is it a control on
this form?"). I think it's a good idea to not depend on implicit
behaviors any more than necessary, particular when being explicit
makes for better code.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/