I am losing work in Access 2003

[Guest]

We have recently upgraded to Access 2003 and recently I have been getting the
error message "Invalid Argument" quite a bit and have actually had forms
revert to previous saved versions even though I've saved my work. To clarify
- I hope - I make changes to forms, save the changes, then close the database
and when I open the database and the form I am getting an older version of
the form as if I never made the changes.

I have tried splitting the database and repairing and compacting. Any idea
of what is going on here? I am not an Access expert but I am a 20+ year IT
professional who thought he was going crazy until it happened more than once.

HELP!!!

 

[Guest]

Do you have the Compact on Close option selected in Tools, Options, General
Tab? If so, disable that option. I bet that you new changes will not go away.
That's the good news. However after then next error or two, do a manual
Compact and Repair. Guess what....

The bad news is that the database is corrupt. Wait! It gets even worse. The
database is getting corrupted because your installation of Microsoft Office
on that computer is bad. This happened to me about a year ago and I tried a
reinstall of Office. Didn't help. Used a tool from MS to completely remove
the old Office install and then reinstalled. No Joy. Finally wiped the hard
drive and reinstalled Windows, Office, and everything else. That worked but
it wasn't a happy experience.

Before doing that though, try working on the database using another
computer. If the problem doesn't happen, you know it's the other PC. If the
database is out on a network drive, you could also try moving it to a PCs
hard drive and seeing it the problem rears its ugly head. Then it just might
be a network problem.

 

[Albert D.Kallal]

About the only things I can think of is that you are perhaps copying the
front end to a cd, and it is read only...

You then copy this "read only" file to a computer...and thus you can edit
data (since it linked to the back end), but
can't make chances to the forms...

Assuming you have split, then you should consider deploying a "mde" to the
users. This will ensure that you at least have
code that can compile...

I explain how to work with, and how to setup a split database here:

http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm

 

[Guest]

Jerry,

Many thanks even if it is bad news. What amazes me is that I can't seem to
find any info on this even though we can't be the only two people on earth
with the problem.

Dave G. (t)

 

[Guest]

Albert,

Thanks for the response, but unfortunately I've pretty much tried all that.
I've got to believe at this point that Jerry is correct and I'll need a
reinstall. I've never seen anything like this. I actually thought that one
of my users - who had similar problems - was off base but now I think perhaps
she has the same problem. As I said in my reply to Jerry, we can't be the
only two people on earth who have run into this yet I can't seem to find any
info on what causes it and what to do other than what Jerry posted.

Dave G. (t)

 

[socrtwo]

Did you try to decompile/recompile the database? The command is:

msaccess.exe /decompile "[path to your database]"

socrtwo
www.s2services.com - data recovery freeware

 

[Tony Toews]

We have recently upgraded to Access 2003 and recently I have been getting the
error message "Invalid Argument" quite a bit and have actually had forms
revert to previous saved versions even though I've saved my work. To clarify
- I hope - I make changes to forms, save the changes, then close the database
and when I open the database and the form I am getting an older version of
the form as if I never made the changes.

Now this is weird. Invalid arguments is usually a sign of a corrupt
record in a table. Mind you forms and such are stored as records in
a system table.

I have tried splitting the database and repairing and compacting.

I'd suggest importing into a new MDB. Repairing and compacting is
more for cleaning up tables rather than other objects.

If that isn't enough then see the following

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

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