I'm running Access 2007, using file format 2002-2003. I don't know how to
look at update levels.

I have an application that is running at a client site. An error has
suddenly appeared at the opening of the most common option. It's a "no
current record" error. I ran this successfully on my computer last week. I
have copies of the application database and the linked file database dating
back to last November. I get this same error on all my copies. I'm
confident I'm not accidentally pointing at the current linked table database
instead of the saved ones because the current one is missing a parameter and
in those cases where I forgot to change the linkage I get the error. I've
exited Access between attempts and I've re-booted. The only thing I can
think of that might have changed is the automatic Microsoft updates. Does
anyone know of a recent update that might have interfered with my system?
How do I look at a record of updates and hunt for those that might have
affected Access?

Does anyone have any other ideas?

Got it. The application is several years old, and I've worked on it a lot
on weekends, but it's gotten pretty stable, and this year I didn't work on
it much. Apparently at the beginning of the 2010 school year I changed it
in a way that would make it impossible to run on a Saturday or Sunday.
That's the answer.

"LAS" <(E-Mail Removed)> wrote in message
news:j1jpdj$hti$(E-Mail Removed)...
> I'm running Access 2007, using file format 2002-2003. I don't know how to
> look at update levels.
>
> I have an application that is running at a client site. An error has
> suddenly appeared at the opening of the most common option. It's a "no
> current record" error. I ran this successfully on my computer last week.
> I have copies of the application database and the linked file database
> dating back to last November. I get this same error on all my copies.
> I'm confident I'm not accidentally pointing at the current linked table
> database instead of the saved ones because the current one is missing a
> parameter and in those cases where I forgot to change the linkage I get
> the error. I've exited Access between attempts and I've re-booted. The
> only thing I can think of that might have changed is the automatic
> Microsoft updates. Does anyone know of a recent update that might have
> interfered with my system? How do I look at a record of updates and hunt
> for those that might have affected Access?
>
> Does anyone have any other ideas?
>

On Sat, 6 Aug 2011 19:53:33 -0400, "LAS" <(E-Mail Removed)> wrote:

>Got it. The application is several years old, and I've worked on it a lot
>on weekends, but it's gotten pretty stable, and this year I didn't work on
>it much. Apparently at the beginning of the 2010 school year I changed it
>in a way that would make it impossible to run on a Saturday or Sunday.
>That's the answer.

Thanks for posting your solution. I was going to post that Access
2010 SP1 was causing some folks problems but that shouldn't matter for
you unless there was some change to ACE.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/