Import not working correctly

  • Thread starter Thread starter rachel
  • Start date Start date
R

rachel

Hi,

I will be doing weekly imports of an Excel 97 spreadsheet
into Access 97. I've been testing the Access 97 import
utility, and I'm finding that it isn't working as it is
supposed to. I'm not getting ANY error reports, even
though I've put values in my spreadsheet that should cause
the "Field Truncation," "Key Violation," and "Null in
Required Field" errors.

Do you know why this could be happening?

Thanks.
 
Hi Rachel,

You say what isn't happening, but you don't say what *is* happening. Is
all or any of the data being imported?


Hi,

I will be doing weekly imports of an Excel 97 spreadsheet
into Access 97. I've been testing the Access 97 import
utility, and I'm finding that it isn't working as it is
supposed to. I'm not getting ANY error reports, even
though I've put values in my spreadsheet that should cause
the "Field Truncation," "Key Violation," and "Null in
Required Field" errors.

Do you know why this could be happening?

Thanks.
Click to expand...

John Nurick [Microsoft Access MVP]

Please respond in the newgroup and not by email.
 
John,

New records are appended to the table, so that part is
working. However, if I then modify a record in Excel and
then try to import it into Access (i.e., I'm trying to
import a record with a duplicate primary key), NOTHING
happens. The modified record does not show up in the
Access table AND I don't get any error messages about
trying to add a record with a duplicate primary key.

Rachel
-----Original Message-----
Hi Rachel,

You say what isn't happening, but you don't say what *is* happening. Is
all or any of the data being imported?


Hi,

I will be doing weekly imports of an Excel 97 spreadsheet
into Access 97. I've been testing the Access 97 import
utility, and I'm finding that it isn't working as it is
supposed to. I'm not getting ANY error reports, even
though I've put values in my spreadsheet that should cause
the "Field Truncation," "Key Violation," and "Null in
Required Field" errors.

Do you know why this could be happening?

Thanks.
Click to expand...

John Nurick [Microsoft Access MVP]

Please respond in the newgroup and not by email.
.
Click to expand...
Click to expand...
 
Rachel,

By the sound of it, then, it's importing the records that "fit" and
silently ignoring the others.

I've just tried importing data that's been edited in Excel and I got the
expectd error messages about field types and key violations. But if
before importing I do
DoCmd.SetWarnings False
the good records are imported and the bad ones ignored.

So the first thing to do is to check that you haven't turned off
SetWarnings elsewhere and failed to ensure that it's turned back on
again. (Better practice is to leave it turned on and program your way
round any errors.)


John,

New records are appended to the table, so that part is
working. However, if I then modify a record in Excel and
then try to import it into Access (i.e., I'm trying to
import a record with a duplicate primary key), NOTHING
happens. The modified record does not show up in the
Access table AND I don't get any error messages about
trying to add a record with a duplicate primary key.

Rachel
-----Original Message-----
Hi Rachel,

You say what isn't happening, but you don't say what *is* happening. Is
all or any of the data being imported?


Hi,

I will be doing weekly imports of an Excel 97 spreadsheet
into Access 97. I've been testing the Access 97 import
utility, and I'm finding that it isn't working as it is
supposed to. I'm not getting ANY error reports, even
though I've put values in my spreadsheet that should cause
the "Field Truncation," "Key Violation," and "Null in
Required Field" errors.

Do you know why this could be happening?

Thanks.
Click to expand...

John Nurick [Microsoft Access MVP]

Please respond in the newgroup and not by email.
.
Click to expand...
Click to expand...

John Nurick [Microsoft Access MVP]

Please respond in the newgroup and not by email.
Click to expand...
 
I'm not too sure what the equivalent is in the user interface. Go to
Tools|Options and experiment with the "Confirm" settings which in Access
2002 are on the Edit/Find tab. If all these are checked I'd expect to
get the warnings about "bad" data.

If they are checked and you still don't get the warnings, it's possible
that a macro (or some VBA code) elsewhere in the database is turning
warnings off for a some particular action but failing to turn them back
on again. In that case you need to search for a macro containing
SetWarnings
and make sure that each
SetWarnings (Warnings On = No)
is followed before the end of the macro by one with Warnings On = Yes.

Likewise if there's VBA in the database, search for DoCmd.Setwarnings
and make sure that they come in pairs too. Post back here if you need
more help about doing that.


John,

This sounds very promising! Just one question: how and
where do I go to change the SetWarnings setting? I've
never messed with the VBA layer of Access.

One more question... Are you working in Access 97? We
are about to upgrade to XP, but I want to figure this
problem out in case I encounter it with the upgraded
version of this database.

Thanks,
Rachel
-----Original Message-----
Rachel,

By the sound of it, then, it's importing the records that "fit" and
silently ignoring the others.

I've just tried importing data that's been edited in Excel and I got the
expectd error messages about field types and key violations. But if
before importing I do
DoCmd.SetWarnings False
the good records are imported and the bad ones ignored.

So the first thing to do is to check that you haven't turned off
SetWarnings elsewhere and failed to ensure that it's turned back on
again. (Better practice is to leave it turned on and program your way
round any errors.)


John,

New records are appended to the table, so that part is
working. However, if I then modify a record in Excel and
then try to import it into Access (i.e., I'm trying to
import a record with a duplicate primary key), NOTHING
happens. The modified record does not show up in the
Access table AND I don't get any error messages about
trying to add a record with a duplicate primary key.

Rachel

-----Original Message-----
Hi Rachel,

You say what isn't happening, but you don't say what *is*
happening. Is
all or any of the data being imported?


On Thu, 4 Sep 2003 12:02:36 -0700, "rachel"

Hi,

I will be doing weekly imports of an Excel 97
spreadsheet
into Access 97. I've been testing the Access 97 import
utility, and I'm finding that it isn't working as it is
supposed to. I'm not getting ANY error reports, even
though I've put values in my spreadsheet that should
cause
the "Field Truncation," "Key Violation," and "Null in
Required Field" errors.

Do you know why this could be happening?

Thanks.

John Nurick [Microsoft Access MVP]

Please respond in the newgroup and not by email.
.
Click to expand...

John Nurick [Microsoft Access MVP]

Please respond in the newgroup and not by email.
.
Click to expand...
Click to expand...

John Nurick [Microsoft Access MVP]

Please respond in the newgroup and not by email.
Click to expand...
 
Back
Top