u canceled previous operation - NO I DIDNT! 1

[DBAchick]

I am on my hands and knees here, hoping someone can help me with this problem.

Running Access 2000 on W2K. I am using a SQL backend by linking tables through an ODBC connection.

I made a lot of changes to my access front end and now everytime I try to do anything (click, select from a drop down, etc) I get the error message: Run-time error '2001': You Canceled the previous Operation.

I have created a new container and imported all of my objects and I still get the error message.

I have compacted and repaired repeatedly to no avail.

I have searched the Microsoft site and have found nothing.

I even moved the .mdf file to another computer and get the same error message.

Please...if someone has any idea what I need to do to fix this, let me know. I appreciate any input.

Thanks!

 

[tlbroadbent]

I suggest that you open one of the modules you are trying to execute. Select the first command line in the module. Press F9 to mark it. The go back to your form and try to run it.

Hopefully, you'll get into the module and stop at the marked command. Press F8 to step through the code noting the last line to execute successfully before the message ooccurs as well as the line where the message occurs.

You may need to go into the References and make sure all of them are pointing to the correct file. Open a VB module and select Tools | References. Terry L. Broadbent
FAQ183-874 contains tips for posting questions in these forums.
NOTE: Reference to the FAQ is not directed at any individual.

 

[LDG1234]

T Broadbent is your man....perhaps he'll here your cry and answer to your plea. I'd be surprised if he can't help. Lloyd Gozzett
Process Developer

 

[tlbroadbent]

DBAChick,

I have a couple of additional questions. Are you using any reserved words in your forms? Are any of the controls on the form named the same as the columns in the table?

Could you post the code from one of the modules that errors? Terry L. Broadbent
FAQ183-874 contains tips for posting questions in these forums.
NOTE: Reference to the FAQ is not directed at any individual.

 

[DBAchick]

I wish I could! The problem is, it occurs everywhere. When I run reports, when I try to open forms in run time and design view. The code that it references as the problem changes every time. I even get the error when I go to File and Close to close the database!

I have since created a new container and imported everything one at a time and tested it. I have come down to one form that if it is in my current .mdf I receive the error. If I delete it and select a different form, everything is fine.

The funny thing is, when I go to import objects from the .mdf that I was having errors with, as soon as I select that file (from Get External Data) I get the error as well.

I am not sure how to proceed from here. Of course the form that is having the issue has the most code behind it and the most controls on it. Should I copy each control over first and then start adding the code one function at a time?

Thank you for all your advise, Terry! I did go in and check the references. I noticed that one of them that was selected on the 'bad' database is no longer available as a choice in the new database file. It is for Microsoft ActiveX Data Objects (Multi-Dimensional) 2.6. I only have 1.0 listed now. I have not selected the 1.0 version and am not having issues at this time. Good Advice though!

 

[ErikZ]

Have you tried to uncompile your database? It sounds like there's a low level error somewhere.

 

[DBAchick]

hmmm, no, I have not tried that because I did not know you could do it!

I was able to recreate the form (what a pain!) and copy the code into it. With a little clean up work, I was able to get it going.

So I guess the answer to this mess is, isolate the form(s) that are causing the issue and create new ones! The worst thing is, all the back up copies I had were corrupt as well so even suggesting to back up more often might not have helped this problem.

Thank you all for your help!!! You are a great asset to the development world!

 

[tlbroadbent]

If you want to try to determine the cause of the error, you could try to force Access to error on a different condition. If you can do that, you may be able to open the problem form. If the form is bound to a table or query, rename the table or query. Then try to open the form. Hopefully, Access will error because the data source doesn't exist.

Another thought - Do you have Option Explicit declared in your modules? You may have an undeclared variable that is causing problems. Terry L. Broadbent
FAQ183-874 contains tips for posting questions in these forums.
NOTE: Reference to the FAQ is not directed at any individual.