>I strongly recommend an atomic primary key (generated) and triggers to

enforce the uniqueness of the N_MOV | MOV_YEAR combination.

could you please expand on this ?

From what you said, I find much easier to add a MOV_YEAR field to the table
and fill it from my D3 program.

>It is a Very Bad Idea to involve dates in keys, too.

not my idea.

The world out there requires that.

Every warehouse movement must be identified by a progressive number that is
unique in the year it takes place.

Every 1st January you restart from no. 1.

>Have you considered buying a good book about SQL? You'll find some

recommendations at http://www.interbase2000.org/bookstore.htm

I have a few books re SQL. Right now I am working with "Database
Developer's Guide" by Ken Henderson at my side which contains a nice
introduction to SQL.

My SQL requirements are - for now - minimal: my goal is to port a DBE
application to IB in the shortest possible time.

When finished, I will enter a second production cycle with the goal of
fully re-writing the whole application for C/S IB.

Then I will have to swim comfortably in SQL :) and the books you recommend
will come handy.

Thank you

Duilio