| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 282.1 | Look under the FILE menu with the database open | CURRNT::BAILEY | Another day, another $ prompt | Mon Jul 19 1993 08:56 | 7 |
| 282.2 | Access will import dBase files which Excel can generate | PEAKS::WELLS | Rick - CXO Storage Subsystems DTN 522-2484 | Mon Jul 19 1993 19:07 | 3 |
| 282.3 | | ROWLET::AINSLEY | Less than 150 kts. is TOO slow! | Mon Jul 19 1993 23:45 | 3 |
| 282.4 | | BUSY::SLAB | A cross upon her bedroom wall ... | Mon Mar 03 1997 12:52 | 20 |
|
MSACCESS 2.0.
I'm trying to import an Excel 5.0 .XLS file into a table and append
it to an existing ACCESS table, but every time I do it I get an al-
most immediate "database corrupt - repair" [paraphrased] error. A
repair works fine, but I still can't append the .XLS file to the
table.
[I want to append it so that I can import the data in the same
format every time and not have to change the column names, since
I'm importing a file with a multi-line title without specifying
that ACCESS should consider the top line as column headers.]
When I import the .XLS file to a new table there's no problem.
Am I doing something wrong?
Thanks for any info.
|
| 282.5 | Duplicate records perhaps? | NSIC00::KLERK | Thunderbirds are Go | Tue Mar 04 1997 04:24 | 12 |
|
Could this have to do with trying to import multiple identical rows?
Since you're trying to append to a table perhaps some XLS rows already
exist. Still I would expect a different type of error then (more like
"duplicate key value not allowed" or such). The fact that importing into
a new table works, suggests your problem may be along thesel lines.
What happens if you import to a new table and then, within Access, try
to append that table to the original one. Does that work or does that
fail too?
Theo
|
| 282.6 | | BUSY::SLAB | Always a Best Man, never a groom | Tue Mar 04 1997 09:34 | 8 |
|
Hmmm, I'll try a separate import/append.
However, I didn't enable a primary key, nor did I specify "no
duplicates".
Thanks.
|
| 282.7 | | BUSY::SLAB | Always a Best Man, never a groom | Tue Mar 04 1997 09:43 | 9 |
|
OK, I opened table 2 and did a left-button drag to copy all the
rows to the copy buffer and then went back to table 1 and tried
to paste them into table 1 and got the exact same error.
"Jet database engine has encountered a problem", or something
like that, if that's any more help than a plain-old corruption
error.
|
| 282.8 | | BUSY::SLAB | An imagine burning in her mind ... | Tue Mar 04 1997 11:05 | 5 |
|
Maybe I'll write both .XLS files to a disk and bring them home
and try them on Windows 95 and Office for Windows 95 and see if
it makes a difference.
|
| 282.9 | | BUSY::SLAB | And when one of us is gone ... | Tue Mar 04 1997 11:19 | 5 |
|
I also tried a copy [both with a left-button drag and copy and a
"select all" and copy] and "paste append" and still got the same
error.
|
| 282.10 | | BUSY::SLAB | Be gone - you have no powers here | Wed Mar 05 1997 00:28 | 11 |
|
Well, I copied the .MDB and .LDB files over to my laptop and conv-
erted the database over to Access V7 and loaded the same .XLS file
into 2 different Access tables ... and successfully copied the data
from table1 into table2 using Paste Append.
So what did I prove by doing this? I don't have a clue, except
that Access V7 can do it and Access V2 can't, as far as I can tell.
I used the same basic database, so apparently there's no inherent
problem with the database itself.
|
| 282.11 | | BUSY::SLAB | Buzzword Bingo | Wed Mar 05 1997 11:13 | 14 |
|
OK, I just created a test database in Access 2.0 and imported 2
Excel 5.0 files to 2 different tables and used copy and Paste
append to add table2 to the end of table1.
So I've ruled out Access2/Excel5 and I've also ruled out yester-
day's database as problems. Both problems have been eliminated
from the equation so it appears that I don't have a problem, ex-
cept for the fact that I still can't do it.
8^)
This is very strange.
|
| 282.12 | | BUSY::SLAB | Can you hear the drums, Fernando? | Wed Mar 05 1997 11:21 | 12 |
|
And I just went into the "problem" database and successfully
import-appended an .XLS file to a table created by that same
.XLS file previously.
I even tried it again and added a blank row to the top of the
.XLS file to see if that would confuse Access, but it worked
fine.
So maybe I don't have a problem after all, or at the most it's
just an annoying fluke that I had the good fortune to discover.
|