Losing Import Specifications - Access 2002

I almost feel stupid posting this, but maybe someone else understands
what's going on here.

I am importing a delimited text file, and have saved an import
specification so that for the user the whole thing is essentially
pushbutton. Except for some reason, it seems my import spec thinks
summer is a good time to pack up and go on vacation, so when the user
tries to run the import, I get error 3265 (missing spec), and the
import obviously fails. If I run an import with a "bad" spec and the
code crashes, does it lose my spec?

The text file I'm importing is fairly simple - essentially a CSV file
with headers. So I guess I could take Chuck's advice and use his
stuff. I was just thinking that this would be simpler...

Any easy way around this, or is this a case of

Patient: "Doc, it hurts when I..."
Doctor: "Well, don't do it, then!"

Thanks
Pieter

I have had some problems getting import specifications to work also. I made
a work around for it. First I import the values into a temporary table.
Next I use an append query to append the values in the temporary table to
the real table with the formatting that I want -- changing data types from
strings to dates, etc.

Hope this helps.

Linda

<pietlinden@hotmail.com> wrote in message
news:1123518573.461057.38450@z14g2000cwz.googlegro ups.com...[color=blue]
>I almost feel stupid posting this, but maybe someone else understands
> what's going on here.
>
> I am importing a delimited text file, and have saved an import
> specification so that for the user the whole thing is essentially
> pushbutton. Except for some reason, it seems my import spec thinks
> summer is a good time to pack up and go on vacation, so when the user
> tries to run the import, I get error 3265 (missing spec), and the
> import obviously fails. If I run an import with a "bad" spec and the
> code crashes, does it lose my spec?
>
> The text file I'm importing is fairly simple - essentially a CSV file
> with headers. So I guess I could take Chuck's advice and use his
> stuff. I was just thinking that this would be simpler...
>
> Any easy way around this, or is this a case of
>
> Patient: "Doc, it hurts when I..."
> Doctor: "Well, don't do it, then!"
>
> Thanks
> Pieter
>[/color]

thanks for the input, but I'm basically already doing that. My "MAIN"
table receives the dirty data, which I can then "wash" using code. It
all works fine. I'm just using the import spec to do the automatable
grunt work.

I know all about the conversion functions, CInt, CLng, ...etc, and
reasonably complex VBA... just no clue how to sort this out.

How do I export an Import Spec? I know it's in one of the hidden
tables... just no clue how to get it out.

I don't know a full, sophisticated answer, but if you go to Tools, Options,
View tab, you can click on "Hidden Objects" and "System Objects" so you can
see the hidden tables.

Linda

<pietlinden@hotmail.com> wrote in message
news:1123538569.415703.5390@o13g2000cwo.googlegrou ps.com...[color=blue]
> thanks for the input, but I'm basically already doing that. My "MAIN"
> table receives the dirty data, which I can then "wash" using code. It
> all works fine. I'm just using the import spec to do the automatable
> grunt work.
>
> I know all about the conversion functions, CInt, CLng, ...etc, and
> reasonably complex VBA... just no clue how to sort this out.
>
> How do I export an Import Spec? I know it's in one of the hidden
> tables... just no clue how to get it out.
>[/color]

Sufficient anyway! Thanks! I knew I was missing something.
(Especially after trying to clean my ears and finding the Qtip came out
the other ear....)

I guess that makes me a Hollow Man... TS Eliot must have me pegged.