Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

TransferText action & delimited text file specifications (A97)

0 views
Skip to first unread message

Roger Mills

unread,
Dec 13, 1998, 3:00:00 AM12/13/98
to
I've lost the Import and Export Text Wizards that I use to create
specifications for determining the format of imported and exported text
files as arguments to the TransferText action. Using the command menu,
importing/exporting of text files goes ahead but the Wizard isn't launched
beforehand - the files are formatted with what I guess is the default
specification.

Does anyone have an insight as to why the Wizards have gone AWOL (I'm
guessing it's a Registry thing) and how I can get them back? I tried
uninstalling Access with the SetUp program and re-installing it but not only
did the Wizards stay absent but I also lost most of the ISAM drivers - which
I only got back by restoring an earlier version of my registry.

And is it really the case that the only way to create specifications for the
import/export of text files is by using the Wizards? I'd have thought that
it could be done in VBA.

Roger

Chris White

unread,
Dec 14, 1998, 3:00:00 AM12/14/98
to Roger Mills
Are you using Win98? I ran into a problem with several ISAM drivers not being
available. I registered them by running Regsvr32.exe. They are all located in
the c:\windows\system folder. Don't have the names of them, but they are all in
the format MSxxxx35.dll.

Chris

Francois Rioux

unread,
Dec 16, 1998, 3:00:00 AM12/16/98
to
>And is it really the case that the only way to create specifications for
the
>import/export of text files is by using the Wizards? I'd have thought that
>it could be done in VBA.


It can.
I used the TABLEDEFS.CONNECT method to attach text files. It would also
work to import them. Using TEXT as the first argument of the connect method
uses the Text installable ISAM driver. The text driver requires a file
named schema.ini to be located in the same directory where the text file to
import is.

Schema.ini looks like any .ini file: the first line contains the name.ext of
the file to import (between brackets) and the following lines contain the
parameters i.e. delimiter = TABDelimited or CSVDelimited or FixedLength;
Characterset = ANSI, etc. You can also define the way dates and numbers are
handled and assign name to columns. The schema.ini can also be used for
exporting tables to CSV files, etc. Search the Access help for the ISAM,
schema.ini and for the connect method and check the examples.

HTMH

Francois

Roger Mills

unread,
Dec 18, 1998, 3:00:00 AM12/18/98
to

Chris White wrote in message :

>Are you using Win98? I ran into a problem with several ISAM drivers not
being
>available. I registered them by running Regsvr32.exe. They are all
located in
>the c:\windows\system folder. Don't have the names of them, but they are
all in
>the format MSxxxx35.dll.


No, Win95. But I install Access on top of Office SBE which I note has
caused others some problems in this area as well.

Have followed your regsvr32 advice and . . . all is now fine. Thanks.

Roger

Roger Mills

unread,
Dec 18, 1998, 3:00:00 AM12/18/98
to

Francois Rioux wrote in message :

>>And is it really the case that the only way to create specifications for
>the
>>import/export of text files is by using the Wizards? I'd have thought
that
>>it could be done in VBA.


>It can.
><snip> Search the Access help for the ISAM,


>schema.ini and for the connect method and check the examples.


Thanks Francois, I missed these references when searching the Help file.
Gives me something new to play with (even though I've got the wizards back)!

Roger

0 new messages