Separate data entry and data edit or not?

I'm using Office 2003 and Windows XP.

It seems to me that data entry should be clearly separated from data edit,
or editing records. I have done this by splitting the entry function and the
edit function into two different forms. Now users load one form to add a new
record and load another to edit an entry already in the DB.

But, I just wanted to get some guru advice on this; is this considered best
practice, worst practice, or does it matter?

Thanks for your input.

Usually I just have one form for both. However it really depends on the
business rules. I created a database for a company where data entry people
could add records but not edit or delete them. Supervisors could only
edit/delete. I made seperate forms mostly as the surpervisors could see a few
more fields than the data entry folks. Of course I also put in user-level
security to allow only certain people to do certain tasks.
--
Jerry Whittle
Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.


"XP" wrote:

I'm using Office 2003 and Windows XP.

It seems to me that data entry should be clearly separated from data edit,
or editing records. I have done this by splitting the entry function and the
edit function into two different forms. Now users load one form to add a new
record and load another to edit an entry already in the DB.

But, I just wanted to get some guru advice on this; is this considered best
practice, worst practice, or does it matter?

Thanks for your input.

I prefer to use one form unless business rules would dictate a separate form
for data entry. The reason I prefer the 1 form approach is for maintenance
issues. If you have two forms, every time you have a change or encounter a
bug, you have two places you have to fix it.

If you want to separate Data Entry from Edits and Deletes by user function,
rather than have two forms, you can set the form's Data Entry property on or
off as needed.

"XP" wrote:

I'm using Office 2003 and Windows XP.

It seems to me that data entry should be clearly separated from data edit,
or editing records. I have done this by splitting the entry function and the
edit function into two different forms. Now users load one form to add a new
record and load another to edit an entry already in the DB.

But, I just wanted to get some guru advice on this; is this considered best
practice, worst practice, or does it matter?

Thanks for your input.