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 TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Using MS Access as an Oracle front end
- Thread starter wrandall
- Start date
wrandall,<br>
<br>
I've been out for a while, but don't see any response here. I've used Access to manipulate Oracle data for several years. Learned early on that while Access is not particularly case-sensitive, Oracle was when it came to creating/naming tables (Oracle v7.1?). Mind, I've not done a great deal of Access to Oracle conversion, but what has been done went very well, the only hangups having been my proclivity to use memo fields in access when smaller text fields would have done just as well.<br>
<br>
Specifically, I was using Access v2.0, ODBC driver for Oracle was InterSolv (was Q+E then) and don't recall the version, probably 2.0 or 2.1. Could not transfer Access relationships or other constraints, but the data transfer was simple, albeit slow.<br>
<br>
There's an upsize wizard app for Access to move to SQL Server, but I'm told that it works equally well (?) moving data to Oracle 7.2 and above. Cannot attest to that directly, but previous experience suggests that there is probably 90% compliance or better for data transfer. You'll likely have to [re]build table relationships, data constraints, etc., but that shouldn't be overly difficult - just tedious.<br>
<br>
<br>
I've been out for a while, but don't see any response here. I've used Access to manipulate Oracle data for several years. Learned early on that while Access is not particularly case-sensitive, Oracle was when it came to creating/naming tables (Oracle v7.1?). Mind, I've not done a great deal of Access to Oracle conversion, but what has been done went very well, the only hangups having been my proclivity to use memo fields in access when smaller text fields would have done just as well.<br>
<br>
Specifically, I was using Access v2.0, ODBC driver for Oracle was InterSolv (was Q+E then) and don't recall the version, probably 2.0 or 2.1. Could not transfer Access relationships or other constraints, but the data transfer was simple, albeit slow.<br>
<br>
There's an upsize wizard app for Access to move to SQL Server, but I'm told that it works equally well (?) moving data to Oracle 7.2 and above. Cannot attest to that directly, but previous experience suggests that there is probably 90% compliance or better for data transfer. You'll likely have to [re]build table relationships, data constraints, etc., but that shouldn't be overly difficult - just tedious.<br>
<br>
I worked with an Oracle 7.3 back end for 4 months recently and you don't talk directly thru ODBC. You have to go thru a layer called SQL Net. This introduces some challenges if you're used to dealing with data on SQL Server. For instance, we were linking to tables on Oracle and SQL Server and the tables on Oracle would appear to be read only when they weren't. It turned out that linking manually to the tables would produce a dialog requesting a unique index for the table. SQL Server doesn't do this, and you don't see it with Oracle from Access when you Link the tables using VB. The solution was to create pseudo indexes for the Oracle tables using the Create Index command. <br>
<br>
If you're used to file server data only this will be a big change.
<br>
If you're used to file server data only this will be a big change.
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Question