The connections are created programmatically then destroyed.
>Hi Everyone,
>
>I just discovered that:
>
>1. ODBC drivers for VFP7 generate "Not a table" error (as expected) due to the new Auto Increment datatype, and
>2. MSFT is not distributing ODBC drivers for VFP 8 (and I assume they won't be creating any).
>
>So, it would seem I need to transition from ODBC TO OLE DB support for my crystal reports. I've read the internal VFP help and some stuff from MSDN but I'm unclear on at least one thing... Is there an OLE DB administrator to create data sources like there is for creating ODBC DSNs in the registry? Or, are the connections only created programmatically only persist until the connection is destroyed? I am aware of how to create a .udl file but this is not an acceptable way for me to provide connection information to my crystal reports.
>
>TIA,
>Jeff
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer