Access Front End Oracle Back End

[itwg]

We want to develop an oracle backend to replace an access back end that we have. We are keeping all the access forms and reports as a front end.

The front end will be stored on the users pc and the backend is on a server.

The question is how do we resolve the user loggin without having to set up a dsn on every pc to the oracle back end. So when someone gets the front end on their machine we don't have to do a dsn connection and they each have a unique username and password?

ITWG

 

[THoey]

ITWG, I am not sure this is possible. You are going to have to put ODBC settings to the database on each machine. You can create logins and passwords in the Oracle database for each user. Give permissions to each of those Oracle logins to have privileges to the tables, etc. Then your Access front end needs to be linked to the Oracle tables.

As for a way to not have to set up a DSN connection on each PC, I don't think that is possible. What about pushing it out to all PC's through something like SMS? Terry
**************************
* General Disclaimor - Please read *
**************************
Please make sure your post is in the CORRECT forum, has a descriptive title, gives as much detail to the problem as possible, and has examples of expected results. This will enable me and others to help you faster...

 

[itwg]

Is there a way of using DSNless connections to the database??

Itwg

 

[AdHoc]

I don't think using a DSN-less connection will allow you to have linked tables. You can open a recordset in VBA but I think you need a DSN on the client computer to link to ODBC tables in MS-Access.

Maybe creating the necessary DSN programatically is the way to go. Go to MSDN and look up the RegisterDatabase method.

http://msdn.microsoft.com/library/d...y/en-us/dao360/html/damthregisterdatabase.asp

It is a DAO method that creates or updates the DSN.

 

[Turkbear]

Hi,
Since each PC will need to have the Oracle Client installed, why not create the ODBC DSN at the same time?



p.s. there are some ODBC drivers that use 'thin client' technology, but they are not cheap. They do not need the Oracle Client to connect so they may be easier in some situations.
try:

http://www.datadirect-technologies.com

 

[Beantree]

I use Oracle 8.17 on W2K db with Access front ends for several apps.

In order to simplify client setup, I use the Oracle NAme Server feature of the DB so that a Service name doesn't have to be configured, but Oracle Client software still needs to be installed. I also use a Service Name backup to the name server.

To simplify the install, I set one up manually, and then copy the TNSNAMES.ORA and SQLNET.ORA files into the appropriate client directory.

 

[itwg]

No, most users will be using MetaFrame, so the Oracle client will only be installed on those servers, with a single DSN on each server. We would still need a way of passing individual user names and passwords through ODBC to the Oracle database.

 

[itwg]

No, most users will be using MetaFrame, so the Oracle client will only be installed on those servers, with a single DSN on each server. We would still need a way of passing individual user names and passwords through ODBC to the Oracle database.

itwg

 

[itwg]

Does anyone have any ideas about my last comment??

ITWG