.How to Change Path to dbf files Using Visual FoxPro ODBC Driver

Question

Using vb.Net 2008, full Crystal 2008.
I have a Crystal report that uses a Visual FoxPro File DSN pointing at a folder with dbase (.dbf) files. 
I need to be able to change the folder location at runtime. In the RDC, one key part of this has been specifying a connection string, such as:
"Driver={Microsoft Visual FoxPro Driver};SourceType=DBF;SourceDB=" & gs_FileDSN_Path & ";Exclusive=No;Collate=Machine;Null=Yes;BackgroundFetch=No;"""""""
However, I can't find any .NET documentation confirming this syntax and, even more importantly, where does it go?
I tried 2 variations as:
                reportTableLogonInfo.ConnectionInfo.Attributes.Collection.Add(New NameValuePair2("Connection String", ls_ConnectionString))
                reportTableLogonInfo.ConnectionInfo.Attributes.Collection.Add(New NameValuePair2("ConnectionString", ls_ConnectionString))
Followed later by   TableN.ApplyLogOnInfo(reportTableLogonInfo)before calling
But I don't know if the correct attribute name is "Connection String", "ConnectionString", or something else.
I also tried to set the connection string to the QE_ServerDescriptions property, as in:
reportTableLogonInfo.ConnectionInfo.Attributes.Collection.Add(New NameValuePair2("QE_ServerDescription", ls_ConnectionString))
None of these variations nr many others seem to work.
BOTTOM LINE:
Could someone provide sample code for overriding the dbase files folder location specified by a Visual FoxPro FileDSN?
Thanks!

Answer 1

OK, I came to the conclusion that the tables or the report somehow hold on to the File DSN for dear life and I can't change that fact.
So I'm going to change my approach and instead of changing the connection properties of the tables, I'll modify the properties of the File DSN on the fly.  Ugly, but an OK solution for my use scenario.
It would still be great to get a code sample for the original question but, it's no longer a burning issue for me.
It would be nice if the support team created a document describing in detail how to achieve database location changes using .NET for different scenarios. It's a common need and the RDC object model had such a document.