[AccessD] Query Puzzler

P.S.  Just got it myself in a Dlookup.  So I guess you can add Domain
functions to the list of stuff that generates this error. 

Rocky

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin
Sent: Sunday, October 11, 2009 10:55 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Query Puzzler

That is one of Microsoft's most cryptic messages.  It actually means, IME,
the current operation.  And usually has indicated to me a problem with the
record source of the form or report.  Or the SQL in a db.Execute.

Rocky

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Arthur Fuller
Sent: Sunday, October 11, 2009 10:32 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Query Puzzler

That may have been a simpler approach, but instead I created a new BE and
imported the old data. (Aside: interestingly, despite the fact that I did a
compact&repair before doing the import, the target db was 2MB smaller than
the source DB. No idea why.) (Aside #2: I'm currently thinking that Bing is
way better than Google.)

In this particular case, the client knows enough about Access to shoot
himself in the foot. How he managed to corrupt the BE while horsing around
eludes me, but he managed. I fixed the corruption and now all is relatively
well. However, fixing the corruption caused a new problem to emerge: Later
in the same procedure I attempt to run a report, and suddenly I'm getting
the error message: "You canceled the previous operation."

Does anyone know what inspires this message?

TIA,
Arthur

On Sun, Oct 11, 2009 at 11:24 AM, Rocky Smolin
<rockysmolin at bchacc.com>wrote:

> I'd be curious to know what would happen if you deleted the indexes 
> from the table and then re-created them.
> R
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Arthur 
> Fuller
> Sent: Sunday, October 11, 2009 7:59 AM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] Query Puzzler
>
> The SQL couldn't be more straightforward, Rocky. It just says "Delete
> * From myTable Where AssessID = 1574". There are 25 matching rows. But 
> since my original post I've been Googling and Allan Browne suggests 
> that this error
> 3709 may indicate a corrupt index. I've created a new BE and imported 
> the data into it. Just checking now to see if that makes the problem 
> go
away.
> Arthur
>
> On Sun, Oct 11, 2009 at 10:48 AM, Rocky Smolin
> <rockysmolin at bchacc.com>wrote:
>
> > Can you post the SQL?
> >
> > Rocky
> >
> >
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com