Why using three tables as you only need one?
And why would you delete employee data?
Here's the columns I'd suggest;
EmployeeID (auto number)
EmployeeName
PIN
StartDate
EndDate
If it happens or could happen that an Employee is re hired, you'd like to move the StartDate and EndDate to a...
No splitting done by yours sincerely ;)
It's simply how the database comes...
As compared to?
I've seen plenty of worse designs in my career, trust me :D
I can't imagine that a world leading company on ERP systems and databases malpractice their designs for no good reasons...
RV
I happen to work with ORACLE systems and customer and supplier data indeed is split up into separate tables.
So the concept does not always necessarily apply ;)
RV
There's absolutely no reason why you would require leading zeros for sorting purposes.
On the contrary, you're much better of without them if you want to sort.
Reason being that you would like to convert text to number in order to sort by number.
If you insist on using leading zeros, search the...
How do you trigger it though
By putting code in it.
If it's not triggered then the code conditions are not met.
If you expect the code to be triggered and it isn't, well, then your code is incorrect ;)
RV
If record 19 is in the current form, simply add a button to the form and follow the wizard.
The wizard will provide you with a choice to open the other form for a specific row.
RV
Either use a query, concatenate both columns in a new column and base your report on the query.
Or add an unbound field to your report and concatenate.
RV
What you need to do is to add foreign key colums to your "many" tables.
Otherwise you can't build any relationships at all.
I suggest you do a bit of reading on how relational databases work.
Also, do read up on normalization as I don't think your current table structure is appropiate.
RV
You could set up security and permissions.
I strongly advise you not to even consider giving users direct access to queries.
This will enable users to screw up your table data.
RV