Preventing Database Lockups

[Sarrkazztic]

We have an Access DB that is pulling data from a form into some tables. The problem we are having is, when users hit the save button at the same time they end up moving to the same next record and the database locks up.

How can we prevent multiple users from falling into the same new record?

 

[Guus2005]

1-Use autonumber columns if you already have done so:
2-Use unbound forms: never fails!

 

[bachgen]

Clarify

1-Use autonumber columns if you already have done so:
2-Use unbound forms: never fails!

Can you clarify what you mean by use unbound forms ?

Thanks.

 

[Pat Hartman]

What do you mean "they end up moving to the same next record"? Access doesn't have a problem with multiple concurrent users. Is something your application doing causing the conflict?

 

[Guus2005]

An unbound form is not connected to a datasource. You must open a recordset and populate the controls yourself giving you the maximum of flexibility. It's a little more work.

When not connected to a single table, i always use unbound forms.

 

[Pat Hartman]

The power of Access lies in bound forms and reports. Creating an unbound form would be the absolute last option on the list of things to try. If you're going to create unbound objects, you may as well be working in vb.net.

 

[Guus2005]

My opinion:

The power of Access lies in the fact that it has a flat learning curve, it is powerful and compact. It gives you the possibility to fast create simple applications. But if you want have more control on what is happening you have to use unbound forms. You don't want to save your record by mistake. I want to leave it at that. This is my opinion.

 

[Pat Hartman]

I guess we can agree to disagree but I can cause or prevent a record from being saved because I know how to use the events available to me in a bound form. I don't need to resort to using an unbound form to exercise that type of control.