By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
428,705 Members | 1,301 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 428,705 IT Pros & Developers. It's quick & easy.

Unable to open / design saved form in Access 2000

P: n/a
Hi,

My problem is the following:

Made changes to code in form and closed the form.

Now unable to open / design the form.

- Tried copying and pasting - the new one does not open /display.
- Tried compacting / repairing but same situation.
- Tried importing to new blank database - the form name appears in the
new db but trying to open it yields a message that the Jet engine
could not find the name of the form.
- Tried running a function looping thru the forms collection and got
bumped out with error code 0 and no error description. Similar loop on
tables ran ok.
This may indicate that there is a problem with the forms collection
but the other forms open normally (thank heaven!).

Could anyone help me rescue the form that contains 2 months of hard
work (yeah, I know.... backups should be made frequently....)?

Thanks,

Eli
Nov 13 '05 #1
Share this Question
Share on Google+
5 Replies


P: n/a
You may want to check out this link. You're not getting the error mentioned,
but it may help. The workaround ought to solve the problem anyway.

http://support.microsoft.com/default...roduct=acc2000

Also, for help with the workaround mentioned, this should make things a
little easier.
http://www.granite.ab.ca/access/corr...uptobjects.htm

And a few more tips that may help.
http://www.granite.ab.ca/access/corruptmdbs.htm

--
Wayne Morgan
Microsoft Access MVP
<el********@hotmail.com> wrote in message
news:8c*************************@posting.google.co m...
Hi,

My problem is the following:

Made changes to code in form and closed the form.

Now unable to open / design the form.

- Tried copying and pasting - the new one does not open /display.
- Tried compacting / repairing but same situation.
- Tried importing to new blank database - the form name appears in the
new db but trying to open it yields a message that the Jet engine
could not find the name of the form.
- Tried running a function looping thru the forms collection and got
bumped out with error code 0 and no error description. Similar loop on
tables ran ok.
This may indicate that there is a problem with the forms collection
but the other forms open normally (thank heaven!).

Could anyone help me rescue the form that contains 2 months of hard
work (yeah, I know.... backups should be made frequently....)?

Thanks,

Eli

Nov 13 '05 #2

P: n/a
Hi Eli

I have had the same problem a few times. This led me to put together a small
add-in utility for using the undocumented SaveAsText and LoadFromText
functions for saving object as text files and reloading them. You can do a
search for on the net to write some code for doing this and I found it
always fixed my problems.

I hate to push a product here, but if you want, the URL is where you can get
a copy of the utility I put together. But you can put the code together
yourself. It is not that hard just to do one object.

http://www.asken.com.au/~askencom/pr...ns/AATB001.php

Jeff

<el********@hotmail.com> wrote in message
news:8c*************************@posting.google.co m...
Hi,

My problem is the following:

Made changes to code in form and closed the form.

Now unable to open / design the form.

- Tried copying and pasting - the new one does not open /display.
- Tried compacting / repairing but same situation.
- Tried importing to new blank database - the form name appears in the
new db but trying to open it yields a message that the Jet engine
could not find the name of the form.
- Tried running a function looping thru the forms collection and got
bumped out with error code 0 and no error description. Similar loop on
tables ran ok.
This may indicate that there is a problem with the forms collection
but the other forms open normally (thank heaven!).

Could anyone help me rescue the form that contains 2 months of hard
work (yeah, I know.... backups should be made frequently....)?

Thanks,

Eli

Nov 13 '05 #3

P: n/a
Hi Wayne & Jeff,

Thanks for your suggestions.

I have tried decompiling the db and then running
Application.SaveAsText with the appropriate parameters for the corrupt
form from within a function. It did recognize the command when I keyed
it, as it prompted me for the parameters needed, but it could not run
it.

SaveAsText was my last hope.

I have probably picked up the wrong tool for development.

Eli
Nov 13 '05 #4

P: n/a
If Access is corrupting things on a regular basis, you have something that
you need to get fixed. Things to look for; bad memory, bad sectors on the
hard drive, improper shut downs, bad network connections.

None of these may cause you a problem under normal operating conditions, but
a database (any database program I've seen) loves RAM. Also, the bad
sector(s) on the hard drive will only show up when you try to access a file
that has been written to that particular sector(s).

If working across a network, Access is designed to do that if done properly.
Also, while the network may seem to be working ok, the amount of data that
you may be transfering with Access may find problems that don't show up with
other items. Access doesn't create the problems, but it will find them if
they exist.

The easiest way to corrupt a file is to have an incomplete write to the
file. Improper shut downs and lock ups on the computer will cause this.
Also, this is why a bad network connection causes problems.

For the hard drive, I recommend that you download the drive manufacture's
testing utility. Most of these are non-destructive (they won't erase your
current data). For the memory check, try http://www.memtest86.com/. Also,
make sure that you have ALL of the latest patches for your operating system,
your version of Office, Jet, and MDAC.

http://windowsupdate.microsoft.com
http://office.microsoft.com/officeupdate/default.aspx
http://msdn.microsoft.com/data/downl...s/default.aspx

The autoupdate sites may have to be run more than once until they say there
are no more updates. Also, did you follow the links in the article I sent
you to? Some of them had tips on preventing corruption, especially if
operating over a network.

--
Wayne Morgan
MS Access MVP
<el********@hotmail.com> wrote in message
news:8c**************************@posting.google.c om...
Hi Wayne & Jeff,

Thanks for your suggestions.

I have tried decompiling the db and then running
Application.SaveAsText with the appropriate parameters for the corrupt
form from within a function. It did recognize the command when I keyed
it, as it prompted me for the parameters needed, but it could not run
it.

SaveAsText was my last hope.

I have probably picked up the wrong tool for development.

Eli

Nov 13 '05 #5

P: n/a
Wayne,

I am running the db on a standalone notebook that has 1.35 GB left
(out of total of 10).
This might have been a contributing factor (or not...).

I have 256MB RAM and I have been running under Windows 98, whose poor
memory management I have been suffering from for years. The reason for
not going XP was mainly drivers.

I had run DiskScan and Defrag not too long ago, but bad sectors do
happen.

Being an Access-ist since version 1.0, I had learned the effects of
turning power off with an open database very long time ago and have
been careful to close the databases with 'all due respect'.

I have not updated my A2K with SPs and will do so tomorrow. From what
they show on the web, these do not tackle the problem I have but I
will nevertheless run them.

Having said all that - the corruption that I have must extend beyond
just the corrupt form. I cannot run a for...next loop that will
display the form names in the forms collection, probably because the
forms collection is corrupt too.

I do not know if Microsoft's people have a way of 'extracting' a
corrupt object in a way other than SaveAsText (which does not work in
my case, either) and I will try talking to them tomorrow.

I will certainly follow your leads re drive and RAM tests.

I realy appreciate your trying to help so much.
Being able to consult knowledgeable people detracts some of the panic.

Thanks again,

Eli
"Wayne Morgan" <co***************************@hotmail.com> wrote in message news:<dt*****************@newssvr22.news.prodigy.c om>...
If Access is corrupting things on a regular basis, you have something that
you need to get fixed. Things to look for; bad memory, bad sectors on the
hard drive, improper shut downs, bad network connections.

None of these may cause you a problem under normal operating conditions, but
a database (any database program I've seen) loves RAM. Also, the bad
sector(s) on the hard drive will only show up when you try to access a file
that has been written to that particular sector(s).

If working across a network, Access is designed to do that if done properly.
Also, while the network may seem to be working ok, the amount of data that
you may be transfering with Access may find problems that don't show up with
other items. Access doesn't create the problems, but it will find them if
they exist.

The easiest way to corrupt a file is to have an incomplete write to the
file. Improper shut downs and lock ups on the computer will cause this.
Also, this is why a bad network connection causes problems.

For the hard drive, I recommend that you download the drive manufacture's
testing utility. Most of these are non-destructive (they won't erase your
current data). For the memory check, try http://www.memtest86.com/. Also,
make sure that you have ALL of the latest patches for your operating system,
your version of Office, Jet, and MDAC.

http://windowsupdate.microsoft.com
http://office.microsoft.com/officeupdate/default.aspx
http://msdn.microsoft.com/data/downl...s/default.aspx

The autoupdate sites may have to be run more than once until they say there
are no more updates. Also, did you follow the links in the article I sent
you to? Some of them had tips on preventing corruption, especially if
operating over a network.

--
Wayne Morgan
MS Access MVP
<el********@hotmail.com> wrote in message
news:8c**************************@posting.google.c om...
Hi Wayne & Jeff,

Thanks for your suggestions.

I have tried decompiling the db and then running
Application.SaveAsText with the appropriate parameters for the corrupt
form from within a function. It did recognize the command when I keyed
it, as it prompted me for the parameters needed, but it could not run
it.

SaveAsText was my last hope.

I have probably picked up the wrong tool for development.

Eli

Nov 13 '05 #6

This discussion thread is closed

Replies have been disabled for this discussion.