Leave them blank there, no need to expose them. Create job parameters (or a parameter set) for the required information - database, user, password (etc) - and then leverage those parameters in your database stages, ODBC or otherwise.
-craig
"You can never have too many knives" -- Logan Nine Fingers
Thanks for the reply. This is actually the approach I currently use. I was just wondering if I could code variables in these entries in odbc.ini that could be resolved at run-time, eliminating the need to pass them as parms.
The question is, what if anything works in the odbc.ini file in some kind of dynamic fashion? Can you leverage a $Something there? I don't believe so but have never tried.
-craig
"You can never have too many knives" -- Logan Nine Fingers