Hi All,

I have two queries:

a) What does this standard action SetODBCFolder do?
b) Do we have any issues / limitations in using the MSI ODBC Tables.
c) Is it a good idea to pass the odbc related information through MSI ODBC Tables or install and capture the registry entries and pass it through the registry table..
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
I don't know for sure, since I never use the ODBC tables but I'd guess that it controls the location of the file used for a file-based DSN (something else I never use!).

In *general*, I've found WI handling of ODBC via the ODBC tables to be sub-optimal and have always used the Registry table instead. YMMV.
Answered 08/11/2009 by: VBScab
Red Belt

Please log in to comment
0
I usually use the registry when creating DSNs. However, if you want to make a DSN using the ODBCxxxx tables, make sure you use both the ODBCDataSource and ODBCSourceAttribute tables to fill out the necessary information.

Here's an example of one of a SQL DSNs I did making use of the ODBCSourceAttribute, ODBCDataSouce tables. Make sure you have a component for your DSN as well.











ODBCSourceAttribute





DataSource_
Attribute
Value



LMS_9.0_SQL
Database
LMS



LMS_9.0_SQL
Server
oursqlserver\sql2005



LMS_9.0_SQL
Description
LMS 9.0_SQL Database



LMS_9.0_SQL
Trusted_Connection
Yes









ODBCDataSource





DataSource
Component_
Description
DriverDescription
Registration

LMS_9.0_SQL
ODBCDataSource4
LMS_9.0_SQL
SQL Server
0

Here's MSDN's blurb. Let me know if I misstated anything.
Answered 08/11/2009 by: elgwhoppo
Senior Purple Belt

Please log in to comment
Answer this question or Comment on this question for clarity