1521 for Oracle
>Witango studio uses a local odbc driver, so it is not WiTango but the >ODBC Driver -> database connection that has been severed. If you look at >the local odbc definition there should be a reference to what port the >odbc driver is using to communicate with the database. >Your DBA should tell you which port the database is listening on. Also >the (so called) network gods should be able to configure the port to be >only accessible from specific IP Address > >Hope this helps > >Ben Johansen - http://www.pcforge.com >Authorized Witango Reseller http://www.pcforge.com/WitangoGoodies.htm >Latest downloads & List Archives @ http://www.witango.ws > > >-----Original Message----- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED]] On Behalf Of [EMAIL PROTECTED] >Sent: Thursday, May 30, 2002 11:37 AM >To: Multiple recipients of list witango-talk >Subject: Witango-Talk: Tango Studio Port Number > >We have an interesting situation in that our network >gods have closed down all ports they don't understand >the use of. This means that my tango studio app can not >communicate with my datasource on the wrong side of the >firewall. Any one know which port tango is trying to >communicate on? > >Thanks, > >John Newsom >> I am going to go hip deep in using TCF. >> >> The point of having objects is reusability. However, if you put a >search in >> a method, doesn't that break the reusability aspects of a TCF since >the >> Search is DB specific? >> >> In other words If I want to use the TCF using a different database, my >table >> names and fieldnames have to be identical to the initial DB in order >to >> enjoy any type of reusability. >> >> Is this correct? >> >> Jose >> -- >> Webologies >> 150 Robinette Drive >> Waynesville, NC 28786 >> 828.627.1994 >> >> http://www.webologies.com >> >> >------------------------------------------------------------------------ >---- >> "You can't make an omelet without breaking eggs" Boris Badenov >> >------------------------------------------------------------------------ >---- >> >> >________________________________________________________________________ >> 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 > > >________________________________________________________________________ >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
