[AccessD] DESPERATE problem with indexes

Hello All,

I wanted to share what just happen...and maybe get some feedback as to why 
it worked.

>In A97 I have a db giving the error "<Db name> isn't an index in this
>table. Look in the Indexes collection of the TableDef object to determine
>the valid index names. (Error 3015)"...I get the error when trying to open, 
>link
>to ,import from ,compact or repair this db...


In doing some research, I saw it mentioned several times...that the reason 
the REPAIR would not work...was that it tried to open the db before 
repairing...the same with importing, linking, and TRANSFERDATABASE.  I tried 
to create links and importing the data with just VBA...unsuccessfully.

Next I tried to edit the DATABASE field in the MSysObjects 
table...(desperate)...thinking I could force the link...(unsuccessful)

At this point I had the corrupt BE on my local machine...and could not open, 
create a link or anything to it...then I got a copy of the FE...which 
already had the links defined for an old location...but same tables...used 
the "Linked Table Manager"...and the links refreshed successfully...I was 
able to use these links to import 100% of the data.

Is my assumption correct...the reason the table manager worked is because it 
did not try to open the db before refreshing the links?

Also...is this a good idea...or just wishful thinking:  Before sending out a 
self contained db...or even a FE/BE db...create a db with copies of the 
empty tables and links to tables in the actual db(location doesn't matter as 
long as you refresh the links and NOT recreate them)...this would make for 
an easy recovery of a corrupt db.

Any insight would be greatly appreciated.

Thanks for all the suggestions,

Mark A. Matte

>From: "Jim Dettman" <jimdettman at earthlink.net>
>Reply-To: Access Developers discussion and problem 
>solving<accessd at databaseadvisors.com>
>To: "Access Developers discussion and problem 
>solving"<accessd at databaseadvisors.com>
>Subject: RE: [AccessD] DESPERATE problem with indexes
>Date: Tue, 13 Jan 2004 11:59:48 -0500
>
>Mark,
>
>   As Andy said, the database is hosed.  You can try JETCOMP.EXE on it and
>that might straighten it out, but it also might not.
>
>I'd simply go to a backup.
>
>Jim Dettman
>President,
>Online Computer Services of WNY, Inc.
>(315) 699-3443
>jimdettman at earthlink.net
>
>-----Original Message-----
>From: accessd-bounces at databaseadvisors.com
>[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Mark A Matte
>Sent: Tuesday, January 13, 2004 10:50 AM
>To: accessd at databaseadvisors.com
>Subject: [AccessD] DESPERATE problem with indexes
>
>
>Hello All,
>
>In A97 I have a db giving the error "<Index name> isn't an index in this
>table. Look in the Indexes collection of the TableDef object to determine
>the valid index names. (Error 3015)"...I get the error when trying to link
>to ,import from ,compact or repair this db...I desperately need to get the
>data out of the db...any ideas?
>
>Thanks,
>
>Mark A. Matte
>
>_________________________________________________________________
>Learn how to choose, serve, and enjoy wine at Wine @ MSN.
>http://wine.msn.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

_________________________________________________________________
Learn how to choose, serve, and enjoy wine at Wine @ MSN. 
http://wine.msn.com/