Database (and backups) not working

[Steve]

I have a new database created in Access 2007. Things were going
swimmingly (or as well as they do for an amateur like me) when
suddenly calculated fields on a form started giving me "?Name# as
their result. Also on click events (eg to open another form) stopped
working.

I don't believe I had made any changes that would cause this but have
been wrong before so went to backups that had also previously worked
and got same error. These backups had worked when saved, had no
changes made at all, hadn't even been opened and suddenly stopped
working!!

Many rebuilds, rewrites etc later I was getting nowhere.

On a whim, I decided to save it as an Access 2007 file (which is what
I thought it already was - *.accdb) and in a different location.

Suddenly all problems gone and everything working again. I then did
the same thing but to my normal location. Everything worked!!

Any one have any idea of whats going on.
This is on a new Vista machine with all office and vista updates and
no Office programs except 2007

[Chris O'C via AccessMonster.com]

You had one or more missing library references. When you converted it to an
accdb, it used the appropriate paths for the libraries for the new file. The
new file works, but the old one and the backups won't until you fix those
missing references.

Chris
Microsoft MVP
Steve wrote:

>I have a new database created in Access 2007. Things were going
swimmingly (or as well as they do for an amateur like me) when
suddenly calculated fields on a form started giving me "?Name# as
their result. Also on click events (eg to open another form) stopped
working.

I don't believe I had made any changes that would cause this but have
been wrong before so went to backups that had also previously worked
and got same error. These backups had worked when saved, had no
changes made at all, hadn't even been opened and suddenly stopped
working!!

Many rebuilds, rewrites etc later I was getting nowhere.

On a whim, I decided to save it as an Access 2007 file (which is what
I thought it already was - *.accdb) and in a different location.

Suddenly all problems gone and everything working again. I then did
the same thing but to my normal location. Everything worked!!

Any one have any idea of whats going on.
This is on a new Vista machine with all office and vista updates and
no Office programs except 2007

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200805/1

[Steve]

On May 28, 7:43*am, "Chris O'C via AccessMonster.com" <u29189@uwe>
wrote:

You had one or more missing library references. *When you converted it to an
accdb, it used the appropriate paths for the libraries for the new file. *The
new file works, but the old one and the backups won't until you fix those
missing references.

Chris
Microsoft MVP

Steve wrote:

I have a new database created in Access 2007. *Things were going
swimmingly (or as well as they do for an amateur like me) when
suddenly calculated fields on a form started giving me "?Name# as
their result. Also on click events (eg to open another form) stopped
working.

I don't believe I had made any changes that would cause this but have
been wrong before so went to backups that had also previously worked
and got same error. * *These backups had worked when saved, had no
changes made at all, hadn't even been opened and suddenly stopped
working!!

Many rebuilds, rewrites etc later I was getting nowhere.

On a whim, I decided to save it as an Access 2007 file (which is what
I thought it already was - *.accdb) and in a different location.

Suddenly all problems gone and everything working again. *I then did
the same thing but to my normal location. *Everything worked!!

Any one have any idea of whats going on.
This is on a new Vista machine with all office and vista updates and
no Office programs except 2007

--
Message posted via AccessMonster.comhttp://www.accessmonster.com/Uwe/Forums.aspx/databases-ms-access/2008...- Hide quoted text -

- Show quoted text -

Thanks for that . Any suggestions on how to find and fix and given I
had done nothing, how it had happened in first place. Note no updates
were done that I am aware of (I know MS can sneak these through now)