P
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
(read american) standards<g>
Figured as much (as long as schema.ini takes precedence, I'm not to
bothered)
thx for the reply
Pieter
Jamie Collins said:Pieter said: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.