[AccessD] Error in Access 2003 that I've never seen before

..would a decompile redo those indexes? ...I'm seeing what I consider as an 
unusually high number of errors in xp to 2003 conversions on a number of 
mdbs.

William

----- Original Message ----- 
From: "Jim Lawrence" <accessd at shaw.ca>
To: "'Access Developers discussion and problem solving'" 
<accessd at databaseadvisors.com>
Sent: Saturday, June 25, 2005 8:08 PM
Subject: RE: [AccessD] Error in Access 2003 that I've never seen before


> Hi John:
>
> Yes, I could not have said it better as that is the obvious reason.
>
> Jim
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of John W. Colby
> Sent: Saturday, June 25, 2005 2:49 PM
> To: 'Access Developers discussion and problem solving'
> Subject: RE: [AccessD] Error in Access 2003 that I've never seen before
>
> If this is an Access container you are discussing, any field used in a
> relationship has an index created on that field by the Jet engine as the
> relationship is created.  This index is hidden.  It simply cannot be seen 
> in
> any way that I am aware of.  Thus if you are discussing a field like this,
> there is likely that hidden index still in existence.
>
> John W. Colby
> www.ColbyConsulting.com
>
> Contribute your unused CPU cycles to a good cause:
> http://folding.stanford.edu/
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Arthur Fuller
> Sent: Saturday, June 25, 2005 5:39 PM
> To: 'Access Developers discussion and problem solving'
> Subject: RE: [AccessD] Error in Access 2003 that I've never seen before
>
>
> I tend to agree, but two puzzles remain (purely in an academic sense -- I
> don't play to lose sleep over them).
>
> 1. The data can't be corrupted since the "bad record" copied intact to the
> Saved As table.
>
> 2. With all the indexes removed, why was it doing an ISAM Seek? One would
> have thought that in the absence of indexes, it would be forced to do a
> table scan. Perhaps that just reveals how little I understand ISAM tables.
> LOL.
>
> Arthur
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence
> Sent: June 25, 2005 2:07 PM
> To: 'Access Developers discussion and problem solving'
> Subject: RE: [AccessD] Error in Access 2003 that I've never seen before
>
> Hi Arthur:
>
> It could be that the record you are trying to delete is not being 
> referenced
> properly; either the field named used is not correct or the table is
> corrupted. It would be caused if the table index did not matching the 
> table
> data. I have only seen it once and I resolved it by exporting all the data
> into a new table, deleting the old and then renaming the new table. Using
> that method excluded a coding or table structure error. Conclusion; Either
> the data or index was corrupted.
>
> HTH
> Jim
>
> -- 
> 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
>