Feasibility of a potential project. Opinions needed!

[Chunk]

First off, I would like to introduce myself. Im a newbie! Im currently studying a degree in computing. I dont know a great deal about Access, but I do know a fair bit about Oracle SQL and I am able to do a fair bit of programming in Java. On top of that, I know a fair bit about database theory, the relational model and SSADM.

I have a huge project on the horizon which im thinking about using Access to develop. However, Ive only ever used Oracle, so I dont know how likely it is that im going to be able to create it in Access.

Is it niave of me to think that because I can create databases in Oracle, and because I understand the realtional model (for the most part), I will be able to easily create something pretty decent in Access?

I know this sounds like an odd thing to ask, but I need some opinions, because all of my teachers are heavily biased towards Oracle, so I cant really ask them.

The project is a basic stock control system that keeps control of items in stock, customers and orders placed by customers. Theres 9 tables and I will have to create forms with subforms, as well as be able to create a database that looks like its running like a stand alone application.

I dont know Oracle SQL inside out, but I know how to create and maintain databases. I know about the realtional model and normalization to 3rd normal form.

So, erm, yeah! What do you all think?

 

[Ron_dK]

I think you might start with the MSAccess sample "Northwind". See how it is build up and modify it to your own needs. More samples are in the Sample Databases on this forum.
If you have any specific questions on tables/queries/etc you might post them in the respective forum section(s).

Good luck.

 

[The_Doc_Man]

If you are familiar with ORACLE and are considering Access, you need to know a couple of differences that might be significant and might not. If neither of these differences are important to you, then your project is, indeed, feasible (unless you plan to have too many users active at once).

1. ORACLE supports data-level "triggers" - Access only supports form/report "events" - so if anyone goes directly into a table, they can make a change that an event won't catch.

2. ORACLE supports "forensic audits" - that let you know who did what to whom when - but Access, because it doesn't support triggers, cannot provide this feature that is normally a crucial part of data assurance.

The only way you can truly protect your data tightly in that environment is if you can block your potential users from seeing the table view. I.e. every action is based on what Access calls a "switchboard" form. You can disable the ability to enter the database panes for tables, queries, etc. BUT then you have to have pushbutton form selection for EVERYTHING.

There are other differences, but from a data security standpoint, these are the two biggies.

Issues of lesser importance are:

3. ORACLE allows more extensive "role-based" options and allows you to combine roles more easily.

4. ORACLE scales to larger machines better. (Heck, if it scales AT ALL, it outshines Access in that regard...)

5. ORACLE allows ODBC incoming connections from Access. Access would probably neither know - nor care - to respond to a request initiated from ORACLE. (But then, if you've got ORACLE, why would you ever ask anything of Access anyway...?)

6. ORACLE out of the box is designed for larger user bases.

7. ORACLE out of the box is able to interact with web pages without having to buy (too much) extra stuff. Pat Hartman, one of our more illustrious members, has a lot more experience with this, though, and could advise you better in this area.

If you can live with that kind of a system, give it a go.