Hi Thearon,
Reference to the time sheet application chapter 12 page 374(ORACLE) I want to cahnge in procedure to accept sequence.nextval instead of
(inTimeSheetID) which is your primary key.
Please advise on how to change the procedure.
I have a trigger to insert the next id(like auto number in access or as identity in SQL).
Second question about ORACLE date:
I have a date field when I enter date as
to_char(1/1/20004,'mm/dd/yyyy') I got error message:
ORA-01843: not a valid month
So I have to write the date as (01-jan-04).
Please advice,
Thanks
Sam

I think nextval will lose its place if the server is rebooted. I'm not aware of a nice feature like autonumber or identity for oracle. Can you post your procedure?

This might help:
http://www-db.stanford.edu/~ullman/f...e/or-time.html

01-JAN-04 is the default format. What we do is have something like this:

Please enter a date (01-JAN-2004): <textbox here>

Sam,

I think the date problem has been answered and the link provided has some useful information. As far as changing the design of the schema and primary keys, I'm afraid you're on your own for that one. My suggestion would be to work the exercises and get everything working. Once you understand the concepts and how everything works then you should feel free to experiment with the design and primary keys.

Thearon