|
Hi
Alan,
Maybe
I misunderstood the question, but if you are going to have WiTango on one server
and the db on another then just (re)configure the ODBC System DSN drivers on the
WiTango server to point to the distant db server.
The
Witango service doesn't know where the database physically resides, just which
ODBC connection to use.
And if
you use the exact same name, uid and pwd for the new odbc connection you
should not even have to touch the Witango server, service or taf files. Things
get a lot more complicated if you don't use the same name, then all the tafs
need to be edited/updated.
I
don't know if there are some r:tango specific additional complicating matters,
but this should work if it's now configured on an ODBC
connection.
Jan
________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf |
- Witango-Talk: database on another server Alan Wolfe
- Re: Witango-Talk: database on another server Garth Penglase
- RE: Witango-Talk: database on another server Jan Magnusson
- RE: Witango-Talk: database on another server Walker, Buddy
- RE: Witango-Talk: database on another server Fogelson, Steve
- Re: Witango-Talk: database on another server Jon van der Raadt
- Re: Witango-Talk: database on another server Jason Schulz
- RE: Witango-Talk: database on another server Jan Magnusson
- RE: Witango-Talk: database on another serve... Garth Penglase
- RE: Witango-Talk: database on another s... Jan Magnusson
- Re: Witango-Talk: database on anot... Steve Smith
- RE: Witango-Talk: database on ... Jan Magnusson
