Import Wizard

[pendell]

I am working with a client running 2003 Access. Some time ago I
built them an import spec for use with the Import Wizard.

Several months later, I have been called back and asked to solve a
problem ... they tried to customize the spec and now the Import Wizard
always fails on the last step (when one presses the 'finish' button),
returning the dialogue box message "Invalid Use of Null".

Running some test, I have determined that the Import Text Wizard fails
for everything, including very elementary csv files, with the same
error message. Whether importing to a new table or into an existing
one, the same failure always
occurs: 'Invalid use of null'. No further information is available.

Has anyone out there ever encountered this error?

--
Respectfully,

Brian P.

[Tom van Stiphout]

On 14 Mar 2007 14:07:11 -0700, pe*****@hotmail.com wrote:

My guess is the import specifications are corrupt.
Try creating a new database and then import a file. Do not yet import
any objects from the old database.

-Tom.

>I am working with a client running 2003 Access. Some time ago I
built them an import spec for use with the Import Wizard.

Several months later, I have been called back and asked to solve a
problem ... they tried to customize the spec and now the Import Wizard
always fails on the last step (when one presses the 'finish' button),
returning the dialogue box message "Invalid Use of Null".

Running some test, I have determined that the Import Text Wizard fails
for everything, including very elementary csv files, with the same
error message. Whether importing to a new table or into an existing
one, the same failure always
occurs: 'Invalid use of null'. No further information is available.

Has anyone out there ever encountered this error?

[pendell]

On Mar 15, 9:56 am, Tom van Stiphout <[e-mail]:

On 14 Mar 2007 14:07:11 -0700, [e-mail] wrote:

My guess is the import specifications are corrupt.
Try creating a new database and then import a file. Do not yet import
any objects from the old database.

Yup, it worked. Created a new database and re-created the import
specifications, and the import worked fine.

Any suggestions on un-corrupting the specs? I tried running the
"repair database" feature and no go -- still getting the same error.
Or should I just rebuild a new database?

And what would cause the corruption in the first place?

--
Respectfully,

Brian P.