Wordpad

  • Thread starter Thread starter Vina
  • Start date Start date
V

Vina

Can someone help me on this, i need to open a file in
wordpad and then save the file. There is something with
my text file that when i import it will say it's too
large but if i open the file in wordpad and then save it
then import then it will import fine.

is this possible in access to have it automated as a
macro or an event?

Any ideas is greatly appreciated.

Thanks
Vina
 
Vina,

Do you get an error message? If so what is it, exactly?

It could be that the file is padded with spaces. Is it
fixed width or what?

I had a similar problem with text files from a Unix
platform. Unix/Linux terminates text lines with a
LineFeed character whereas PC's use a CarriageReturn
LineFeed pair of chars (Mac's use a CR on it's own just to
confuse matters further).

If I opened the file with TextPad then saved it as PC ANSI
all was fine.

I also found that Access 2000 and 97 handle text files
differently on Win9x(95, 98, 98SE, ME) platforms from
WinNT platforms(NT, 2000, XP). My app would import the
Unix Oracle export on Acc97 on Windows95 but not Acc97 on
WinNT.

You may also have a problem on NT platforms if the file
suffix is .DAT. Rename it if so.

Nick Coe, Lincoln, UK
Accessing for far too long
 
Nick,

It says record too long or overflow. And yes it has to do
something with the carriage return, i think. It is a
delimited file.

It can be imported fine with access 2000 but i cannot use
access 2000 for this. I have to use access 97.

What did you do to fix your problem?

So i was wondering if i can let access automaticall open
wordpad and then just hit save before importing then it
works fine.

Thanks
Vina
 
What about using Word?

If that will work, you can use Automation to open the file
and save it.

Chris Nebinger
 
Vina,

It was importing the UNIX file as a single line of text
and thus as a single record.

Before actually suggesting something specific I strongly
recommend you get an editor like TextPad which will let
you open the file in Hex mode and see exactly what is at
the end of each line. This could affect what is best for
you to do next.

I'm not at all sure what I did is an appropriate solution
to your problem yet.

I wrote some vba using the Text and Line Class modules
from the Access Developers Handbook by Getz, Litwin and
Gilbert published by Sybex, modified it to import
individual chars aswell as lines and then stepped through
each char parseing out the data I wanted and losing any
line terminaton chars.

Nick Coe
Lincoln UK
Accessing for too long...

classicnick at yahoo dot com
-----Original Message-----
Nick,

It says record too long or overflow. And yes it has to do
something with the carriage return, i think. It is a
delimited file.

It can be imported fine with access 2000 but i cannot use
access 2000 for this. I have to use access 97.

What did you do to fix your problem?

So i was wondering if i can let access automaticall open
wordpad and then just hit save before importing then it
works fine.

Thanks
Vina
Click to expand...
SNIPPED
 
Back
Top