Data entry Form

[drunkenneo]

I am working on Data entry form where a user can enter the details in the form and save and go ahead, its a single form in default view. I want to provide an edit button with navigation control in this form only where they can edit their wrong record for update. Hw can i acheve this?

[June7]

Not sure what you are asking for. Do you want to find and go to an existing record?

[drunkenneo]

In this form when user submits the filled form gets saved and a blank for is opened for new entry and in between if user wants to correct the details which he previously entered, can go back and update the record.

But i have provided a form with default look as a single not continous. Hw can i proceed with it?

[June7]

What do you mean 'blank form is opened' - isn't the form already open and simply moved to a new record row? Can't they use the navigation buttons at bottom of form to move back to the record just saved? You can code a button to do the same thing. Can also have an unbound textbox or combobox to enter search info and code to find record.

[drunkenneo]

What do you mean 'blank form is opened' - isn't the form already open and simply moved to a new record row? Can't they use the navigation buttons at bottom of form to move back to the record just saved? You can code a button to do the same thing. Can also have an unbound textbox or combobox to enter search info and code to find record.

Yes, you got it correct, i have did the task of navigation with an array, the form is used as front end, i have got the ways, thanks 4 respknse june 7 i willsurely ask if i face somthing new

[Missinglinq]

Like June7 and the other 50 people that have read this, I'm not sure of exactly what you're trying to do! Exactly what does "submits the filled form" entail? Is this a Bound Form, and does 'submit' merely mean 'save' the Current Record? If so, and the Form is not being immediately Requeried, as June7 said, you merely have to navigate back to the Previous Record, using the native navigation button or a custom navigation button:

Private Sub Go2PreviousRecord_Click()

  If Me.CurrentRecord = 1 Then

    MsgBox "There Is No Previous Record!"

  Else
  
    DoCmd.GoToRecord , , acPrevious

  End If

End Sub

Linq ;0)>

[drunkenneo]

Not sure what you are asking for. Do you want to find and go to an existing record?

Let me go one by one thos time...

I am making a data entry app in access, where i have made a form to given to user as front end.

This for is default is single form where user is displayed new row in this case the form is blank where user needs to only input and button is provided on pressing it will append by an insert query.

When user wants to rectify the mistake of previously emtered data, then on same form i want the user to use navigation button on edit mode to search to and fro..
And yes here came my main challene where i want user to press an correction button , on pressing it form should be open in edit mode and can navigate through users entered record and update the corrections.

I was stuck on the part of correction button where user sees the form shows the records which usere entered. Any nice solution on this?

[June7]

Why are you using an INSERT query to save record? If form is bound to table, and controls are bound to fields, the entered data passes directly to table - no code required.

[Missinglinq]

I agree! Several developers I know, experienced in Visual Basic, C++ and Access database development, estimate that development, using Unbound Forms, by highly experienced developers, takes two to three times as long, as it does when using Access and Bound Forms. That's because with Bound Forms, Access takes care of the 'heavy lifting,' but with Unbound Forms, the developer has to write code to take care of just about everything. If this were a Bound Form, as we've said, you'd only have to move to the Previous Record, to correct the Previous Record, rather than searching for it!

If you insist on using Unbound Forms, you'd be far better off using a straight VB or C++ front end with a SQL Server or Oracle back end.

• You can create an EXE file which gives total protection to your code/design
  
• You can distribute the db to PCs without a copy of Access being on board
  
• Your data security is far, far better than anything you can do in Access

Linq ;0)>

[drunkenneo]

Wow, thats a lot of information you all have given, i havent bound forms, because of the reason in the case i need to check the duplicates records also which may be entered by another user need to check when submitting the record and there is user name also entered in the table which is static (here i am not using any login and password window as they have such requirement).

But you guys are awsome i came to know many things which i wasn't aware of.

[Missinglinq]

...i havent bound forms, because of the reason in the case i need to check the duplicates records also which may be entered by another user need to check when submitting the record and there is user name also entered in the table which is static (here i am not using any login and password window as they have such requirement).

This is usually the answer given for using Non-Bound Forms, and to be honest, it's simply a bogus argument! There is very little in the way of data manipulation, including checking for duplicates, that you cannot do using Bound Forms, and usually with much less code. This is usually done in the Form_BeforeUpdate event. In a Bound Form, this event fires immediately prior to the Record being saved; if something is amiss, you Cancel the Update and allow the user to fix the problem.

Linq ;0)>

[drunkenneo]

In the case what happens if 50 users enter data at same time and in this condition two users are entering same data at same time.

[Missinglinq]

I've been doing this for over a decade and have never had a record duplicated when validating it. The Form_BeforeUpdate event fires a nanosecond before the Record is saved, and the odds of two users, entering identical data, having the event and the check for duplicates fire at the exact same point in time is simply astronomical in scope! And what's to say that using code, to loop through an entire Recordset, as you'd have to do with an Unbound Form, is any less likely to allow two identical Records to be saved at the exact point in time?

One of the major advantages of using Access is that it is allows for Rapid Application Development. As stated before, if you're going to insist on using Unbound Forms, and giving up the RAD advantage, you'd be much better off using a VBA or C++ front end with a SQL Server or Oracle back end. Going the Unbound route, in Access, is like buying a turbo-charged sports car and using it for a newspaper delivery route!

Linq ;0)>

[drunkenneo]

Hi Missinglinq, i am working for bound, i want to have a static username for updation and also a flag i want to insert, depending on the condition that records have. that need to be done on Form_afterinsert event right?