Stumping Microsoft - Text Delimiter in Schema.ini

[jthornton]

So far Microsoft is stumped but they are on their way and I am awaiting an answer.

You can refer to "Exporting Text Files" a few topics down from this one that was posted.

I have created a Schema.ini file through code to override the default export specs in the registry for a text file. The parameter "TextDelimiter=" is used to set the default text delimiter which is a double quotes around the text. They found "TextDelimiter=" in some kind of non public database but they haven't found the value that turns the double quotes off when exporting a text file. I am doing this through code so that a Export Specification does not need to be created and managed for every new query. It is being designed for a flexible user application.

Good luck in figuring it out before Microsoft.

[JHausmann]

Check out :
http://www.vb-world.net/ubb/Forum3/HTML/002033.html


[This message has been edited by JHausmann (edited 11-02-1999).]

[Mongo]

Re: Exporting via a schema.ini

See:
Demo based on Robert Smith's "Export To Anything" tip for DAO first published in VBPJ(US) Feb 1998

Creator: Robert Smith [email protected] http://smithvoice.com/vbfun.htm
demo posted 3/1999

[jthornton]

Thanks for the replies and all of that information has been helpful because I have used it already to make it this far. I called Microsoft and they finally found the parameter "textdelimiter=" for the schema.ini file. The only problem is that we couldn't figure out what setting to pass to it so that there is no delimiter like the option {none} in the Import/Export Wizard. We can change to anything including a space. They did tell me that in Jet4.0 it is possible to set it to "none" but in Jet 3.5 it is not. All I want to do is create a comma delimited text file without any text delimiter. I downloaded the files that you recommended but I don't have VB to run them. I am assuming though that this "textdelimiter=" option was not demonstrated.

Do you have any ideas?

Thanks very much so far for your time

[SmithVoice]

Well, there is a workaround for Jet3x, I think you've considered it already. Instead of forcing an empty string for the text field delimiter, use an alternate character that is most likely not going to be found in your source data such as:

[fred.txt]
FORMAT=Delimited(,)
TextDelimiter= ^
ColNameHeader=True

With this you get a ^ text field delimiter with Jet3. Whe you need to work with the file you can quickly write the same Schema.ini to the file location, then your DAO will know that the ^ is the text delimiter.

-Smith