MS-DBase Drivers distribution - URGENT

Hi,
I am using WISE5.0g (latest) for creating my installation kit, and I chose DBase ODBC32 Driver for distributing drivers with the kit. My setup program also updates the registry to create the DSN.
After the installation I got some errors related to ConfigDriver,ConfigDSN ... I had to add some more DLLs like the MSJET35.DLL,MSJTER35.DLL,MSJINT35.DLL AND MSXBSE35.DLL
to get my Dbase DSN configurable in the ODBC Adminstrator..
However, after installation when I run my application,
I get "Error 3170 : Cound't find installable ISAM..."
My Questions :
1 .Will anyone pls let me know the possible cause for the problem ?
2. What is the list of files to be added in the setup for DBase distribution.
3. What are the registry changes required to set up the DBase drivers / DSN ?
4. Lastly what will be the difference in the answers to the above questions if the driver version changes ????

Thanks for taking out your precious time..
gianapaAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
lekshmikrConnect With a Mentor Commented:
Note   If your application cannot work correctly with the default functionality of the Microsoft Jet database engine, you may have to change the settings in the Windows Registry to suit your needs. The Windows Registry can also be used to tune the operation of the installable ISAM and ODBC driver.
      ..
You can modify the settings in the Windows Registry in three different ways. First, you can simply use Regedit.exe to overwrite the default settings which are established when the Microsoft Jet database engine is registered. This method of modification is the least flexible, because all applications which use the Microsoft Jet database engine have these new default settings.
The second method of modifying the Windows Registry settings is to create a Microsoft Jet portion in your application's registry tree to manage the settings for the Microsoft Jet database engine. The easiest way to accomplish this is to export the existing Microsoft Jet key and then import it into your application's tree with the Regedit.exe Export and Import commands. You can then alter any values you want to specify in your new registry tree. If you have supplied any values in the Engines subfolder, Microsoft Jet loads those settings when the application starts. Any values not entered in your client application's registry tree are loaded from shadow settings.
In order for your application to load the appropriate portion of the Windows Registry key you must specify the location with the DAO INIPath property. Your application must set the INIPath property before executing any other DAO code. The scope of this setting is limited to your application and can't be changed without restarting your application.

The following table shows possible database types and their corresponding database specifiers and paths for the Connect property setting. You can also specify “FTP://path/etc.” or “HTTP://path/etc.” For the path. In an ODBCDirect workspace, only the "ODBC" specifier can be used.
Database type      Specifier      Example

Microsoft Jet Database      [database];      drive:\path\filename.mdb
dBASE III      dBASE III;      drive:\path
dBASE IV      dBASE IV;      drive:\path
dBASE 5      dBASE 5.0;      drive:\path
Paradox 3.x       Paradox 3.x;      drive:\path
Paradox 4.x      Paradox 4.x;      drive:\path
Paradox 5.x      Paradox 5.x;      drive:\path
FoxPro 2.0      FoxPro 2.0;      drive:\path
FoxPro 2.5      FoxPro 2.5;      drive:\path
FoxPro 2.6      FoxPro 2.6;      drive:\path
Excel 3.0      Excel 3.0;      drive:\path\filename.xls
Excel 4.0      Excel 4.0;      drive:\path\filename.xls
Excel 5.0 or Excel 95      Excel 5.0;      drive:\path\filename.xls
Excel 97      Excel 97;      drive:\path\filename.xls
HTML Import      HTML Import;      drive:\path\filename
HTML Export      HTML Export;      drive:\path
Text      Text;      drive:\path
ODBC      ODBC;DATABASE=database;UID=user; PWD=password;DSN= datasourcename;[LOGINTIMEOUT=seconds;]      None
Exchange      Exchange; MAPILEVEL=folderpath; [TABLETYPE={ 0 | 1 }];[PROFILE=profile;][PWD=password;][DATABASE=database;]      drive:\path\filename.mdb
      ..
Remarks
If the specifier is only "ODBC;", the ODBC driver displays a dialog box listing all registered ODBC data source names so that the user can select a database.
If a password is required but not provided in the Connect property setting, a login dialog box is displayed the first time a table is accessed by the ODBC driver and again if the connection is closed and reopened.
For data in Microsoft Exchange, the required MAPILEVEL key should be set to a fully-resolved folder path (for example, "Mailbox - Pat SmithIAlpha/Today"). The path does not include the name of the folder that will be opened as a table; that folder’s name should instead be specified as the name argument to the CreateTable method. The TABLETYPE key should be set to "0" to open a folder (default) or "1" to open an address book. The PROFILE key defaults to the profile currently in use.




Note   If your application cannot work correctly with the default functionality of the Microsoft Jet database engine, you may have to change the settings in the Windows Registry to suit your needs. The Windows Registry can also be used to tune the operation of the installable ISAM and ODBC driver.
      ..
You can modify the settings in the Windows Registry in three different ways. First, you can simply use Regedit.exe to overwrite the default settings which are established when the Microsoft Jet database engine is registered. This method of modification is the least flexible, because all applications which use the Microsoft Jet database engine have these new default settings.
The second method of modifying the Windows Registry settings is to create a Microsoft Jet portion in your application's registry tree to manage the settings for the Microsoft Jet database engine. The easiest way to accomplish this is to export the existing Microsoft Jet key and then import it into your application's tree with the Regedit.exe Export and Import commands. You can then alter any values you want to specify in your new registry tree. If you have supplied any values in the Engines subfolder, Microsoft Jet loads those settings when the application starts. Any values not entered in your client application's registry tree are loaded from shadow settings.
In order for your application to load the appropriate portion of the Windows Registry key you must specify the location with the DAO INIPath property. Your application must set the INIPath property before executing any other DAO code. The scope of this setting is limited to your application and can't be changed without restarting your application.

0
 
gianapaAuthor Commented:
Adjusted points to 75
0
 
lekshmikrCommented:
Check your [Installable ISAM] section in your ini file is correct
0
 
gianapaAuthor Commented:
Now that was fine..
Some DLL was corupted ...
Thanks..

0
 
gianapaAuthor Commented:
And yes, I add the 'JET' key under Microsoft key in the system registry..
'lekshmikr', Please provide me with more details for the answer that you have given..I think if I understand your suggestion I will give you the points :-)

Thanks..



0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.