Is the "Log File" connection string parameter still valid in OWC11?

I'm adding this to the connection string and not getting anything:
"...; LOG FILE=C:\OLAPLOG.TXT;"

I've also tried adding " around the file name since it appears in the
XMLData parameter on the web page.

Thanks!

______________________
Terry Smith
Senior Architect
Insight Ecosystems

Hi Terry,

I've just run some test and it's definitely valid.

Two points to take a look at:
1. Although in OLEDB Connection String Syntax it is said that all
leading and trailing spaces around keywords and values are ignored, but
they are actually removed from the connection string at run time, the
final semicolon as well. Depending on how you use the object, it might
help to remove the spaces yourself.
2. If the file name has other extension than txt or log, .log is
appended. However, TXT is considered different from txt so the created
log file is actually OLAPLOG.TXT.log

HTH,

Eugen

OLEDB Connection String Syntax:
http://msdn.microsoft.com/library/de...ringsyntax.asp

Are you looking for the log file on the c: drive on the web server or on
the client's c: drive? You should find the log file on the client's c:
drive as that is where the OWC ActiveX control is running.

--
Regards
Darren Gosbell [MCSD]
Blog: http://www.geekswithblogs.net/darrengosbell

In article <AB72799E-025B-4EA1-A7C3-1E9EFF59D199 (AT) microsoft (DOT) com>,
TerrySmith (AT) discussions (DOT) microsoft.com says...