Niall,

You can edit the TAF files manually with a text editor and do a search and
replace on the DSN's in the XML code. But be careful.

Your database actions reference the DSN's like this:
<SearchAction UseDevelopmentDataSource="TRUE" DSID="devdb"
DeploymentDSID="depdb" ID="mySearchAction" Sig="srch">

The datasource definitions are like this:
        <!--Data sources-->
        <DataSources>
                <DataSource ID="depdb">
                        <DSType>ODBC</DSType>
                        <DSN>mydb</DSN>
                        <DBMS />
                        <Host>sysdb</Host>
                        <Database />
                        <UserInfo Encrypted="True">
                                <UserName />
                                <Password />
                        </UserInfo>
                </DataSource>
        </DataSources>

You should be able to leave the DSID the same on the database action and
datasource definition, and just change the <DSN>, <UserName> and <Password>
attributes on the deployment ds definition. You'll have to set <UserInfo
Encrypted="False"> also.

Dave.

> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Niall Merrigan
> Sent: Thursday, May 16, 2002 9:31 AM
> To: Multiple recipients of list witango-talk
> Subject: RE: Witango-Talk: DSNs
>
>
> Thanks guys
>
> This leads me onto my second question.
>
> I have files that were developed on a server with different DSNs to
> deployment.  Anyway of changing them globally without running them through
> teh tango editors.
>
> And my third
>
> Where does wiTango get teh username and passwords it need to access the
> DB, does it get them from the ODBC or does it store them somewhere
>
> Cheers
>
> Niall
>
>
>
>
> On Thu, 16 May 2002, Trevor Green wrote:
>
> ->You can specify DSN Name, user and password using Tango variables. To do
> ->this double click the datasource in your .taf file. Where you see "Set
> ->deployment datasource", select "Specify" and unselect "Same as
> ->development". The parameters for the deployment datasource will become
> ->available for editing. You can populate them with a specified string or
> ->a variable. For example:
> ->
> ->Type: ODBC
> ->Name: <@var local$DSN>
> ->User: <@var local$User>
> ->Password: <@var local$password> <- the password can be tricky as it only
> ->shows password characters so you need to ensure that you type it in
> ->correctly.
> ->
> ->Regards
> ->Trevor
> ->
> ->-----Original Message-----
> ->From: Niall Merrigan [mailto:[EMAIL PROTECTED]]
> ->Sent: 16 May 2002 02:05
> ->To: Multiple recipients of list witango-talk
> ->Subject: Witango-Talk: DSNs
> ->
> ->Hi all,
> ->
> ->Just wondering.  If there anyway to include a file giving either the
> ->connection string or dsn name so that tango can use it.  This means I
> ->would be able to change the name of the DSN withiout having to edit the
> ->Tafs.
> ->
> ->Regards
> ->
> ->Niall
> ->
> ->
> ->
> ->
>
> --
> Niall Merrigan
>
> Newest Mix Releases & Track Listings @ http://nm.csn.ul.ie/tunes
>
>
>
>
>
>
> ________________________________________________________________________
> TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
>                 with unsubscribe witango-talk in the message body

________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
                with unsubscribe witango-talk in the message body

Reply via email to