Thanks, Bill. I tried your suggestion, but the new DB displayed the same behavior. I found that the corrupt DB had a new table called MSysCompactError added after a Compact and Repair Database. There was one record in it. It had an ErrorCode of -1002, ErrorDescription is '|' is not a valid name. Make sure that it does not include invalid characters or punctuation and that it is not too long. There is no ErrorRecid. The ErrorTable is MSysRelationships.
I went back a backup that I'd made earlier and it worked. Where or what this error is is not obvious. I can't see the MSysRelationships table.
Thanks again for your help
Terryomsn
--- In MS_Access_Professionals@yahoogroups.com, "Bill Mosca" <wrmosca@...> wrote:
>
> Terry
>
>
>
> It could be index corruption, system corruption...who knows. Import everything
> into a new, blank database. That usually cleans up mysterious errors like that.
>
>
>
> Regards,
>
> Bill
>
>
>
> From: MS_Access_Professionals@yahoogroups.com
> [mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of Terry Olsen
> Sent: Thursday, March 22, 2012 8:33 AM
> To: MS_Access_Professionals@yahoogroups.com
> Subject: [MS_AccessPros] Access 2007 & Errors Using the Import Wizard for Text
> Files
>
>
>
>
>
> Hi
> Up until yesterday, the Import Wizard has performed flawlessly in each of my
> four databases.
> On one database, I received a message saying " was an invalid name. Check to see
> if the name was too long or illegal. I imported the same file into a fresh DB
> and it worked fine. I've repaired and tried, but to the same result.
> On the second database, I'm starting to receive a subscript out of range error
> when import/appending. This has worked numerous times before.
> Is there something that I should be doing other than compact and repair, which I
> do weekly on each database?
> Thanks for any insights.
> Terryomsn
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
Tidak ada komentar:
Posting Komentar