entering a range of invoices

[warco]

I am creating an inventory database and each entry has an individual invoice # and a few other informative fields. Quite often there will be 20+ entries with consecutive invoice #s and all other fields will be indentical. Is there any way to enter these records into a table without having to enter each invoice one by one.

I was also wondering if their would be a way to make a form button that would duplicate that record for the next record only adding 1 to the invoice #. Kind of like an optional autonumber.

A solution to either of these dilemnas would make my database a success. I have a feeling these problem are very basic, but I have been only using access for 2 days.

 

[KingKong]

warco,

Try this thread for 'autonumber':

http://www.access-programmers.co.uk/forums/showthread.php?s=&threadid=40609

And this for 'default value':

http://www.access-programmers.co.uk/forums/showthread.php?s=&threadid=18210

Credits go to Talismanic and WayneRyan.

Grtz,

Peter.

 

[neileg]

Please don't double post
http://www.access-programmers.co.uk/forums/showthread.php?s=&threadid=51972

 

[KingKong]

I h*te double posts, that's actually one I've forgotten !!

(check this thread at The Watercooler)

http://www.access-programmers.co.uk/forums/showthread.php?s=&postid=199747

 

[warco]

thanks neil and King kong for your help, but I have read both of your solutions and I feel that WayneRyan and Tal's solutions may be too advanced for me. Neil your solution sounds like it would solve my problem, but I do not understand what "PK" is.

I was wondering if you could give me some insight on how to build an expression which when I click on the form's "duplicate" button it would just add 1 to my last entered invoice number (always numeric)and keep all other field entries the same.

Thanks for your speedy replies and I am making progress everyday on my database forms and with your help they will soon be working efficiently, so please don't give up on me.

 

[warco]

success

just wanted to say thanks for all the help. I just worked through some trial and error creating a macro, but now everything runs smooth and efficient.

 

[neileg]

Sorry for the jargon. PK is primary key, ie a unique identifier for each record that is used by the database to relate records together.

When the primary key of one table is held as a field in another table to refer to a record, it is known as a foreign key, FK.