Hi all,
I've spent lots of time over the past month developing a database that does exactly what I need it too, except for one problem which no one seems to be able to resolve. So ... i'm going to start from scratch and get some up-front advice on how to design this application.
I need to create a very simple data entry form that will allow users to fill in the fields, then save the data to a new row in the db, preferable by clicking a button that says "save". Instead of having them type in the info from scratch, I would like them to be able to navigate thru the rows and pick one that is close to what they currently need to enter. They will then make some changes to the existing row ... but instead of updating the current row, it will save to a new row.
It really is a simple problem ... but due to a non-resolvable problem in my previous post, i am asking for advice on how best to design this. If you would like to see my current problem with the "old" solution, please see http://www.access-programmers.co.uk/forums/showthread.php?t=70390
but like I said, i just want advice from you experts on how this (what I thought would be very simple) application should be designed.
I've spent lots of time over the past month developing a database that does exactly what I need it too, except for one problem which no one seems to be able to resolve. So ... i'm going to start from scratch and get some up-front advice on how to design this application.
I need to create a very simple data entry form that will allow users to fill in the fields, then save the data to a new row in the db, preferable by clicking a button that says "save". Instead of having them type in the info from scratch, I would like them to be able to navigate thru the rows and pick one that is close to what they currently need to enter. They will then make some changes to the existing row ... but instead of updating the current row, it will save to a new row.
It really is a simple problem ... but due to a non-resolvable problem in my previous post, i am asking for advice on how best to design this. If you would like to see my current problem with the "old" solution, please see http://www.access-programmers.co.uk/forums/showthread.php?t=70390
but like I said, i just want advice from you experts on how this (what I thought would be very simple) application should be designed.