"You Canceled the Previous Operation"

I have an Access database that basically runs select queries using
different criteria inputted by the user. It's not a very complex
database, but it is used by 10-15 users. Recently our department was
upgraded from Office 2000 to Office 2003. Around that time, users
would receive the "you canceled the previous operation" message box
when trying to run the primary query. (Originally there was another
issue, and I had IT restore the database from a date prior to the
upgrade). Do you think the issue is because the database is corrupt or
because of the upgrade? If it's because of the upgrade, can anyone
advise on how to handle this? Thanks.

Coll wrote:
> I have an Access database that basically runs select queries using
> different criteria inputted by the user. It's not a very complex
> database, but it is used by 10-15 users. Recently our department was
> upgraded from Office 2000 to Office 2003. Around that time, users
> would receive the "you canceled the previous operation" message box
> when trying to run the primary query. (Originally there was another
> issue, and I had IT restore the database from a date prior to the
> upgrade). Do you think the issue is because the database is corrupt or
> because of the upgrade? If it's because of the upgrade, can anyone
> advise on how to handle this? Thanks.

I usually get that when I mis-specify a domain aggregate function:
DMax("ColumnNameMisspelled","Table","Field = 2")

Possibly the restored database has a renamed or missing column the query is
looking for?

On Jun 30, 8:52*pm, "Frank" <nos...@buildit.com> wrote:
> Coll wrote:
> > I have an Access database that basically runs select queries using
> > different criteria inputted by the user. It's not a very complex
> > database, but it is used by 10-15 users. Recently our department was
> > upgraded from Office 2000 to Office 2003. Around that time, users
> > would receive the "you canceled the previous operation" message box
> > when trying to run the primary query. (Originally there was another
> > issue, and I had IT restore the database from a date prior to the
> > upgrade). Do you think the issue is because the database is corrupt or
> > because of the upgrade? If it's because of the upgrade, can anyone
> > advise on how to handle this? Thanks.
>
> I usually get that when I mis-specify a domain aggregate function:
> DMax("ColumnNameMisspelled","Table","Field = 2")
>
> Possibly the restored database has a renamed or missing column the query is
> looking for?

Hi - I'll take a look, but I don't think that's the case. The database
has been running smoothly for over a year, and I hadn't made any
changes recently. After the db was restored, it worked fine for a
lilttle bit, and then the issue surfaced. I'll check though.

When there's no obvious cause, and no associated change, we may be in
guess mode. Here are mine (guesses that is):

1. The database is corrupt: seems unlikely as you describe something
that worked and now doesn't;
2. Something got renamed; How about auto-spell? Maybe in 2003 auto-
spell has decided that some object named "smth" really should be named
"smith" and has renamed it, neglecting to tell the rest of the
application; I've never had the slightest problem with auto-spell but
many have been reported;
3. Something is missing; when I cut and paste I often leave out the
last or first line or character; perhaps you did something like that
when you converted?

I think a full decompile may find any such problem. I tend to step-
over this solution and to go directly to the one below.

My experience is that SaveAsText, LoadFromText is more often than not,
a universal cure for such problems, that is, saving an object as text
and reloading it from text will either work smoothly, in which case
the object is likely to be golden, or not work, in which case the
problem object has been identified.

Perhaps, you can't identify any particular object to test, and need to
check everything. Code at http://www.ffdba.com/downloads/Save_...ts_As_Text.htm
is an example of how to do this. I strongly recommend that such code
be avoided unless you are at level where you can understand what it is
doing and assess its suitability for you application. I don't need to
tell you that such code should be used only on a copy of a database,
but such a caution might be helpful for some other reader.

On Jul 1, 9:28*am, Coll <col_mcma...@hotmail.com> wrote:
> On Jun 30, 8:52*pm, "Frank" <nos...@buildit.com> wrote:
>
> > Coll wrote:
> > > I have an Access database that basically runs select queries using
> > > different criteria inputted by the user. It's not a very complex
> > > database, but it is used by 10-15 users. Recently our department was
> > > upgraded from Office 2000 to Office 2003. Around that time, users
> > > would receive the "you canceled the previous operation" message box
> > > when trying to run the primary query. (Originally there was another
> > > issue, and I had IT restore the database from a date prior to the
> > > upgrade). Do you think the issue is because the database is corrupt or
> > > because of the upgrade? If it's because of the upgrade, can anyone
> > > advise on how to handle this? Thanks.
>
> > I usually get that when I mis-specify a domain aggregate function:
> > DMax("ColumnNameMisspelled","Table","Field = 2")
>
> > Possibly the restored database has a renamed or missing column the query is
> > looking for?
>
> Hi - I'll take a look, but I don't think that's the case. The database
> has been running smoothly for over a year, and I hadn't made any
> changes recently. After the db was restored, it worked fine for a
> lilttle bit, and then the issue surfaced. I'll check though.

Coll wrote:
> On Jun 30, 8:52 pm, "Frank" <nos...@buildit.com> wrote:
>
>>Coll wrote:
>>
>>>I have an Access database that basically runs select queries using
>>>different criteria inputted by the user. It's not a very complex
>>>database, but it is used by 10-15 users. Recently our department was
>>>upgraded from Office 2000 to Office 2003. Around that time, users
>>>would receive the "you canceled the previous operation" message box
>>>when trying to run the primary query. (Originally there was another
>>>issue, and I had IT restore the database from a date prior to the
>>>upgrade). Do you think the issue is because the database is corrupt or
>>>because of the upgrade? If it's because of the upgrade, can anyone
>>>advise on how to handle this? Thanks.
>>
>>I usually get that when I mis-specify a domain aggregate function:
>>DMax("ColumnNameMisspelled","Table","Field = 2")
>>
>>Possibly the restored database has a renamed or missing column the query is
>>looking for?
>
>
> Hi - I'll take a look, but I don't think that's the case. The database
> has been running smoothly for over a year, and I hadn't made any
> changes recently. After the db was restored, it worked fine for a
> lilttle bit, and then the issue surfaced. I'll check though.

Do all users get this message for any run of the query? Or is it
specific users or specific records...like vendor is Joe and date is
tomorrow? Are all service packs the same? Is there anyway you can
debug.print current SQL when it blows up thru some error trapping? That
way you could run the SQL produced but the debug.print statement in a
query.

On Jul 1, 10:22*am, lyle fairfield <lyle.fairfi...@gmail.com> wrote:
> When there's no obvious cause, and no associated change, we may be in
> guess mode. Here are mine (guesses that is):
>
> 1. The database is corrupt: seems unlikely as you describe something
> that worked and now doesn't;
> 2. Something got renamed; How about auto-spell? Maybe in 2003 auto-
> spell has decided that some object named "smth" really should be named
> "smith" and has renamed it, neglecting to tell the rest of the
> application; I've never had the slightest problem with auto-spell but
> many have been reported;
> 3. Something is missing; when I cut and paste I often leave out the
> last or first line or character; perhaps you did something like that
> when you converted?
>
> I think a full decompile may find any such problem. I tend to step-
> over this solution and to go directly to the one below.
>
> My experience is that SaveAsText, LoadFromText is more often than not,
> a universal cure for such problems, that is, saving an object as text
> and reloading it from text will either work smoothly, in which case
> the object is likely to be golden, or not work, in which case the
> problem object has been identified.
>
> Perhaps, you can't identify any particular object to test, and need to
> check everything. Code athttp://www.ffdba.com/downloads/Save_MDB_Objects_As_Text.htm
> is an example of how to do this. I strongly recommend that such code
> be avoided unless you are at level where you can understand what it is
> doing and assess its suitability for you application. I don't need to
> tell you that such code should be used only on a copy of a database,
> but such a caution might be helpful for some other reader.
>
> On Jul 1, 9:28*am, Coll <col_mcma...@hotmail.com> wrote:
>
>
>
> > On Jun 30, 8:52*pm, "Frank" <nos...@buildit.com> wrote:
>
> > > Coll wrote:
> > > > I have an Access database that basically runs select queries using
> > > > different criteria inputted by the user. It's not a very complex
> > > > database, but it is used by 10-15 users. Recently our department was
> > > > upgraded from Office 2000 to Office 2003. Around that time, users
> > > > would receive the "you canceled the previous operation" message box
> > > > when trying to run the primary query. (Originally there was another
> > > > issue, and I had IT restore the database from a date prior to the
> > > > upgrade). Do you think the issue is because the database is corruptor
> > > > because of the upgrade? If it's because of the upgrade, can anyone
> > > > advise on how to handle this? Thanks.
>
> > > I usually get that when I mis-specify a domain aggregate function:
> > > DMax("ColumnNameMisspelled","Table","Field = 2")
>
> > > Possibly the restored database has a renamed or missing column the query is
> > > looking for?
>
> > Hi - I'll take a look, but I don't think that's the case. The database
> > has been running smoothly for over a year, and I hadn't made any
> > changes recently. After the db was restored, it worked fine for a
> > lilttle bit, and then the issue surfaced. I'll check though.- Hide quoted text -
>
> - Show quoted text -

Thanks for all of the suggestions. I created a new database in 2003
and imported everything into it. Working for the moment. If that one
starts to produce the msg box, then I will use this suggestions to
research further. To answer the questions from "salad" - I don't know
if all users have the problem, but I know at least 4 (including me)
all began receiving the message at the same point, so I"m assuming all
receive it. Just to complicate things, I went into the database to see
if the problem occurred on all queries or just the main one - now it's
working fine...I'll stick with the new version and will use these
suggestions if the database causes further problems. Thanks.