>Here are my thoughts:
>
>1. Run GenDBC to make an empty copy of a database.

I would not use GenDBC to do this, but this is a possibility.

Personally, I keep an empty copy of the database handy, and make all structural changes there. That makes it simple to then update the changes (APPEND FROM for each table), a) in a directory I use for testing, b) at the client site (or shared folder in a network).

>2. I need a select statement to select two most recently run jobs per each job type, I'm not sure, how to write this select. I do not remember, if the Jobs table has a timestamp, but I want to have recent jobs per each type. Some jobs could be run year ago (for some job type), but I still want them, since I want to have every possible Job Type.

I am not so sure whether this can be done with "standard" SQL... I think this has been discussed a few days ago. For a single record in each group, it should be simpler: max(...) and GROUP BY. But it should be fairly simple to write a UDF that uses structural programming to select the PKs of the last two records in each group.

>3. Once I have JobIDs with these jobs, I can create selects for all related tables and then append from the resulting cursors...

Yes, I think that would be the procedure to follow.