Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Connection to Oracle.. without using DSN..

Status
Not open for further replies.

Alleyopp

Programmer
Sep 17, 2004
22
US
Ok, this is probably a stupid question but bear with me..

I have a VB6 front end with an Access back end and I also connect to an Oracle DB..

It is time to do the build and right now we are building the Oracle ADO connection string using DSN..

Is there a way to not have to worry about puting a DSN and updating the TNSNames file on each users machine?

In other words I would like to build a connection string to Oracle that has everything in it so I dont need to have a DSN on the users machine or update their TNSNames file..

Is there a way to do so??
If not then what is the best was to build and distribute this? We have about 20 users right now.. It would be a pain to have to manually create a DSN and update each TNSNames file for each..

Any help would be great..
And yes, please explain in simple English..
An Example would be great..

TnsNames:
DEV =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = thomas.j9.mil)(PORT = 1522))
)
(CONNECT_DATA =
(SERVICE_NAME = devel)
)
)
 
I already have..
It does not explain about the DSN and TNSNames file and how they fit into the picture..
 
The DSN is fully explained on the link posted, and the DSNLESS connections do work well with Oracle 9 and 10 at least.

As for TSNNAMES.ORA that is a Oracle file and it is REQUIRED and needs to be well configured.
There are ways for you automate the distribuition of files into client machines. Search the web or design it your self.

Just as an example your install application can create a default TSNNAMES entry to a "install" server and then connect to it and retrieve the information for the production server, and update the local TSNNAMES.ORA with the correct information.




Regards

Frederico Fonseca
SysSoft Integrated Ltd
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top