Steve, try the steps suggested here:
Recovery sequence - Standard steps to recover a database
at:
http://allenbrowne.com/recover.html
Follow through them in order. You may also need to move onto the SaveAsText
solution.
Let us know how you go.
--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"Steve S" <SteveS[ at ]discussions.microsoft.com> wrote in message
news:4D67AC86-DC46-48C1-9485-A51369D38CA4[ at ]microsoft.com...
[Quoted Text] > Have one form (out of about 20) that sometimes causes 100% CPU usage after
> a
> seemingly small design change. Can't close the form or switch out of
> design
> view. Get the message something like "Can't perform this operation at
> this
> time" The only way to kill access (2000) is via the Task Manager which
> shows
> 100% CPU usage and only access running.
>
> The change can be something as minor as the as resizing a field or
> changing
> some vba code.
>
> when I open the app again the change that caused the problem seems to have
> saved and the form operates normally.
>
> Doesn't happen every time but enough to be very aggravating.
>
> Any help is appreciated
> --
> Steve S
|