HR Interim Database - for Oracle import later?

snoopydoopy

New member
Local time
Yesterday, 21:32
Joined
Oct 23, 2014
Messages
9
Hi Guys.
I'm designing a massive a database with a multitude of tables, the employee number is >60,000 say.
Now - from my understanding as this is to be imported for Oracle later, I should stay away from Access specific functions - i.e. Lookups importantly.
I understand comboboxes are ok? as they are based on a table? Or am I wrong there too.. and should stay away from that.
More importantly, due to the sheer size of employees - will i manually have to select from the combobox - as I will not be able to do that for that many employees?
- so that is the question, should i be using combo-boxes and if so, can they be auto-linked for example, to the right department without manually selecting for each employee?

ps. As it is to be imported into an oracle/sql database later - what other things or functions should i stay from?
 
You can set the combo box source to be filtered down by a department and even a further sub-department, office location or anything else that is stored per employee - so that should keep things manageable.

You would set these up as cascading combo boxes, or list boxes - there are dozens of examples on here on how to do it.
 
Other Access-specifics, off-hand, to be avoided like the plague:

  1. Multivalued fields
  2. Spaces or non-alphanumeric characters in object or field names
  3. Attachment fields
  4. And as you mentioned: lookup fields in tables


For comboboxes with many items, Allen Browne has advice. Google his site - it's a veritable goldmine (which is why I did not give you the specific link).

He also has a take on using Byte or Integer instead of Boolean
 
I used Access with Oracle extracts and ODBC for several years. Avoid the stuff you mention and have well designed (and tested) tables and relationships.
Can you tell us more about how your Access and Oracle will fit in the overall application?

You can certainly work with Oracle as the BE (linked tables), and Access as FE. You can also work with pass through queries to Oracle (Oracle SQL dialect).

Good luck with the project.
 

Users who are viewing this thread

Back
Top Bottom