Careful when working with MS Access and production level database systems like Oracle, MS SQL, and MySQL. Access has file size limitations (4gb) and does not have a robust server engine to power through data. Attaching an Access front end to an Oracle back-end is kinda like attaching a 2 cylinder engine to a freight load.
I have to ask why would you need to attach Access to your Oracle db? Reporting? Data entry forms? What ever your requirement, take this warning with you as you develop: Any database configuration that includes MS Access is NOT production quality. Microsoft continually adds/drops major functionality from it's office product. Anything you develop in Access 2007 will not convert cleanly to Access 2010 or 2012 ect. Access lacks the advanced data management and multi-user support essential for deploying a production-level database.
I have spent YEARS rescuing inconsistent, orphaned, and black-boxed data trapped in Access databases. I've seen companies become married to multiple versions of Access simply because the key functionality on which a solution was built was not continued in the next version. I'm talking Access 1.0 - 2007. Although it's kept me gainfully employed, I'd rather fine tune well-built databases than keep rebuild Access-based data solutions.
Please consider developing your front-end in an established programming language as a desktop application or a web UI. Think about using industry standard reporting tools like SSRS,Crystal Reports, or Business Objects. If it's worth doing, it's worth doing right.
1
