Paul Rodgers
Paul.Rogers at SummitMedia.co.uk
Mon Aug 23 05:14:26 CDT 2004
Hi John Sorry to be so long in replying. We had a big server crash. Your memo field idea seems to be exactly it. Instead of copying just the structure and appending, desperation had me replace the most suspect memo with a text field instead - and suddenly it was a friendly table, happy to be copied a million times. That's a quirk I won't forget in a hurry. Many thanks, John. Thanks too to Messrs Marty Connelly, Joe Hecht, jim dettman, and John Bartow. All the best paul -----Original Message----- From: Colby, John [mailto:JColby at dispec.com] Sent: 17 August 2004 17:17 To: 'Access Developers discussion and problem solving' Subject: RE: [AccessD] A table that can't be duplicated Are there any memo fields in the table? If so that may be the problem, memos get corrupted. If that is the case it is one or more specific memos (specific records). The easiest way to determine is to create the table structure only (empty) in another db then append all the records to that table. If there are corrupt memos the copy will fail. JWC -----Original Message----- From: Paul Rodgers [mailto:Paul.Rogers at SummitMedia.co.uk] Sent: Tuesday, August 17, 2004 11:47 AM To: 'Access Developers discussion and problem solving' Subject: [AccessD] A table that can't be duplicated The main table in a database won't be copied. Access says another user is busy with the table. But this is not so. I can't copy the table and rename the table, I can't import it into another database, I can't use a MakeTable query to do it that way. etc etc --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.742 / Virus Database: 495 - Release Date: 19/08/2004