KB#00263-'I/O error during save' error when creating a Data Source via Microsoft Query
'I/O error during save' error when creating a Data Source via Microsoft Query
Using MSQuery 8 that ships with Office 97 to create a new Data Source the following error may result:
I/O error during save. You have typed an invalid file name!
Most likely what is happening is that the ODBC Administrator is attempting to save the File DSN file with a double extension:
Another symptom of this problem is that the Data Sources are not showing up in MSQuery when they are created in the ODBC Administrator under File DSN.
Create a User DSN in the ODBC Administrator. Once this has been done, the next step is to create a File DSN that doesn't contain any configuration information - just a pointer to the User DSN that you just created. This way the Data Source will be available from applications that use DSNs as well as from applications that use File DSNs. An additional benefit is that you only have to maintain one DSN. Here's how to do this:
1) Find out where the File DSNs are kept. In later versions of the ODBC Administrator, this can be accomplished by clicking on the File DSN tab. It will have a "Look in:" dropdown box that contains the directory where the File DSNs are stored. This is typically "C:\Program Files\Common Files\Odbc\Data Sources".
2) Create a new text file in that directory. This can be done with wordpad or any other ASCII editor. The filename should refer to the name used when setting up the User DSN, for consistency, and end with a "dsn" extension.
3) Edit the file. The contents of the file should be as follows:
Where the portion following DSN= points to the User DSN that has already been created.
4.) Verify under Explorer, View, Options,View tab that the "Hide file extensions for known file types " is not selected. Check the file name for a double extension. Rename the file if necessary.
Last Modified: 07/27/1998 Product: BASIS ODBC Driver Operating System: Windows
BASIS structures five components of their technology into the BBx Generations.