Hello.

I am saving an Excel file as a text file then importing it into Access
using a specification. One of the fields in the file is a currency
formatted with commas. Those numbers over 999 are being interpreted
as text and not imported. I could modify the Excel file not to use
the commas before I import, but I was looking for something more
automated.

I tried making it a text field in the specification, but it still only
imported those numbers under 1,000.

Any help would be appreciated.

Thanks.

I found the problem. Thanks.

On Jan 23, 11:59=A0am, angelasg <asguill... [at] gmail.com> wrote:
> Hello.
>
> I am saving an Excel file as a text file then importing it into Access
> using a specification. =A0One of the fields in the file is a currency
> formatted with commas. =A0Those numbers over 999 are being interpreted
> as text and not imported. =A0I could modify the Excel file not to use
> the commas before I import, but I was looking for something more
> automated.
>
> I tried making it a text field in the specification, but it still only
> imported those numbers under 1,000.
>
> Any help would be appreciated.
>
> Thanks.

Might help some other participant here, in the future, if you'd say what the
problem was and how you fixed it. Newsgroups are for sharing information,
not just for getting free help.

Larry

"angelasg" <asguillory [at] gmail.com> wrote

I found the problem. Thanks.

angelasg <asguillory [at] gmail.com> wrote in news:38302a66-fb6e-45de-9a46-
0127cbc5da1a [at] f47g2000hsd.googlegroups.com:

> I found the problem. Thanks.

Was it in that column headed, "It's ALL about ME!"?

"lyle fairfield" <lylefa1r [at] yah00.ca> wrote

>> I found the problem. Thanks.
>
> Was it in that column headed, "It's ALL about ME!"?
>
It recorded the International Database Safety Administration finding of
"Pilot Error."