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

Error: You cancelled the previous operation

P: n/a
I've received this error several times, and have only been able to get
around it by deleting the offending form(s) and importing them from backup -

Here's the sequence:
1. I'm editing a form or code in a form module in MSAccess2000 on Win2k
Terminal Server.
2. When I try to save, I get the "Save As" dialog box instead of a regular
save. I click Cancel. I never know when this will occur, it's happened 3
or 4 times in 6 months.

After this if I try to open the form I get the error msg "Compile Error: You
cancelled the previous operation" a number of times, and then I get "Module
not found".

If I try to open the form in design mode, nothing happens. Renaming isn't
allowed.

I've tried repair compact, jetcomp.exe and decompiling all without success.

I noted an old post that mentioned dlookup not making sense of criteria
causing this error msg, but that doesn't seem to be the case here, though I
may be missing something.

Any help understanding this would be greatly appreciated,
Thanks,
John
Nov 13 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Given the symptoms you describe, the error message does indicate some kind
of corruption. The problem may not be completely preventable in Access 2000,
but these ideas may help.

To recover, try exporting the corrupted form to text, with the undocumented
SaveAsText. Then create a new (blank) database, turn off the Name
AutoCorrect boxes (Tools | Options | General), import the other objects
(File | Get External | Import), and then try retrieving the failed form with
LoadFromText. Set the minimal references you need, and check that the
application compiles.

For suggestions on preventing corruption, see:
http://members.iinet.net.au/~allenbrowne/ser-25.html
#2 and #5 are the most likely causes for the case you describe.
#4 is also crucial, and may be a factor in a Terminal Server environment.

--
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.

"John A." <ja********@nomailhere.net> wrote in message
news:Unq1d.745$t61.78@clgrps13...
I've received this error several times, and have only been able to get
around it by deleting the offending form(s) and importing them from
backup -

Here's the sequence:
1. I'm editing a form or code in a form module in MSAccess2000 on Win2k
Terminal Server.
2. When I try to save, I get the "Save As" dialog box instead of a regular
save. I click Cancel. I never know when this will occur, it's happened 3
or 4 times in 6 months.

After this if I try to open the form I get the error msg "Compile Error:
You
cancelled the previous operation" a number of times, and then I get
"Module
not found".

If I try to open the form in design mode, nothing happens. Renaming isn't
allowed.

I've tried repair compact, jetcomp.exe and decompiling all without
success.

I noted an old post that mentioned dlookup not making sense of criteria
causing this error msg, but that doesn't seem to be the case here, though
I
may be missing something.

Any help understanding this would be greatly appreciated,
Thanks,
John

Nov 13 '05 #2

P: n/a
Allen,
Thank you for such a thoughtful answer full of good suggestions. I'm not
currently corrupted and did indeed find that Name Auto Correct had not been
disabled in this particular project. Also found a subform in the offending
form that didn't have a text box for the field in the LinkChildFields
property of the subform.

When corrupted the project did indeed act as if it were still in break mode,
much like your description under point 5 in your 'Preventing Corruption'
list.

When the Terminal Server clears out tonight, I'll create a new db with
NameAutoCorrect off and move all objects - hopefully that will be the end of
it.

Thanks again for your cogent assistance,

John
"Allen Browne" <Al*********@SeeSig.Invalid> wrote in message
news:41***********************@per-qv1-newsreader-01.iinet.net.au...
Given the symptoms you describe, the error message does indicate some kind
of corruption. The problem may not be completely preventable in Access 2000, but these ideas may help.

To recover, try exporting the corrupted form to text, with the undocumented SaveAsText. Then create a new (blank) database, turn off the Name
AutoCorrect boxes (Tools | Options | General), import the other objects
(File | Get External | Import), and then try retrieving the failed form with LoadFromText. Set the minimal references you need, and check that the
application compiles.

For suggestions on preventing corruption, see:
http://members.iinet.net.au/~allenbrowne/ser-25.html
#2 and #5 are the most likely causes for the case you describe.
#4 is also crucial, and may be a factor in a Terminal Server environment.

--
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.

"John A." <ja********@nomailhere.net> wrote in message
news:Unq1d.745$t61.78@clgrps13...
I've received this error several times, and have only been able to get
around it by deleting the offending form(s) and importing them from
backup -

Here's the sequence:
1. I'm editing a form or code in a form module in MSAccess2000 on Win2k
Terminal Server.
2. When I try to save, I get the "Save As" dialog box instead of a regular save. I click Cancel. I never know when this will occur, it's happened 3 or 4 times in 6 months.

After this if I try to open the form I get the error msg "Compile Error:
You
cancelled the previous operation" a number of times, and then I get
"Module
not found".

If I try to open the form in design mode, nothing happens. Renaming isn't allowed.

I've tried repair compact, jetcomp.exe and decompiling all without
success.

I noted an old post that mentioned dlookup not making sense of criteria
causing this error msg, but that doesn't seem to be the case here, though I
may be missing something.

Any help understanding this would be greatly appreciated,
Thanks,
John


Nov 13 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.