SELECT INTO to text file

[RB Smissaert]

I have no trouble getting data from Interbase with the ODBC connection.
My whole app relies on that.
Trouble is getting the right syntax to output to text.
I am not using a schema.ini and I found sofar that this gets produced
automatically in the process, so I didn't have to do it.

I will put post some of my efforts + error messages later.

RBS

 

[Pieter Wijnen]

one more thing
SELECT A.* INTO
[Text;Database=C:\Temp\;TextDelimiter=none;ColNameHeader=True;Format=TabDelimited;].[MyTables#txt]
FROM...

seems to ignore the TextDelimiter parameter (works fine if I edit
schema.ini)
Do you know anything about this?
Not the biggest problem to workaround, but annoying...

Pieter

 

[Pieter Wijnen]

Found a bit here..

http://office.microsoft.com/en-us/assistance/HP010321661033.aspx

Pieter

 

[Pieter Wijnen]

so we (outside the US) must as per usual make workarounds for "universal
(read american) standards<g>
Figured as much (as long as schema.ini takes precedence, I'm not to
bothered)

thx for the reply
Pieter

one more thing
SELECT A.* INTO
[Text;Database=C:\Temp\;TextDelimiter=none;ColNameHeader=True;Format=TabDelimited;].[MyTables#txt]
FROM...

seems to ignore the TextDelimiter parameter (works fine if I edit
schema.ini)
Do you know anything about this?

Sure, you can put all sorts of rubbish in the connection string and the
driver will ignore it <g>.

Seriously, I think it is merely popular myth, perpetuated in seemingly
respectable MSDN articles, that such properties may be made in the
connection string.

Following this article

http://www.dicks-blog.com/archives/2004/06/03/external-data-mixed-data-types/

I occasionally see ONEDAYWHEN appearing in connection strings. Popular
myths are easily (accidentally) made!

Jamie.