How to ignore write conflict error message and close form

[Richard-S]

I have to say that it seems you are racing towards a train wreck. The different scenarios using RDP, runtime, etc. will work. However, you will experience interesting things. As for using a Runtime Exception as a way to catch an overwrite, I cannot say that sounds dependable or convenient. Be aware that when there is a runtime exception that all variables will lose their handle and be destroyed. So a string variable that you dimensioned and initialized will become nothing. This may give someone using the full version of Access a false hope that things are normal.

I did not know that about runtime and variables. Thanks. The group may be more restricted than planned. One thing they have avoided is a full beta test using whatever devices they have. The group plans to ask volunteers to bring what they have in laptops or iPads and then be hooked up. Even if this program works with a few devices, it is hard to know what will happen with more bidders. It already seems with every minor change I make something new emerges. And it does appear that when 2 bids are made for the same item at the same second, there is going to be a collision.

Question - In the situation I have, is there any program difference using a query or a table as form data? I am using a query because there is one criterion needed and although I have used tables, there does not seem to be a difference in speed or data updating the table.

[ItsMe]

There is not one single answer for tables vs. queries. In general, you do not ever want to do a complete table dump and retrieve all the records from a table. So, you implement a query to retrieve certain data. On the other hand, binding a form to a table object is not a terrible thing when you are appending records. Just use the form's data entry property to restrict the records retrieved.

I would add that when I recognize issues as described, I look to the design of the database and the design of the application for possible causes.

[rpeare]

I am late to this conversation but I didn't see it mentioned.

I am assuming you are using a bound form, have you considered using an unbound form? That way the only time your data is touched is when you perform a specific event. So let's say you have two users. they both open the same record and have it open, on a bound form this is going to create a problem for the second person to close the record. In an unbound form, as long as the 'save' event occurs with a fraction of a second differential you should be able to perform all the checks you need to and prevent this write error altogether. This is why I favor unbound forms, with multiple users it really prevents a lot of these conflicts.

[Richard-S]

I am late to this conversation but I didn't see it mentioned.

I am assuming you are using a bound form, have you considered using an unbound form? That way the only time your data is touched is when you perform a specific event. So let's say you have two users. they both open the same record and have it open, on a bound form this is going to create a problem for the second person to close the record. In an unbound form, as long as the 'save' event occurs with a fraction of a second differential you should be able to perform all the checks you need to and prevent this write error altogether. This is why I favor unbound forms, with multiple users it really prevents a lot of these conflicts.

True, I am using a bound form. I'll see how an unbound form will work. This has been a very educational (and fun) project where events that seem simple at start evolve into odd problems. I had no idea certain objectives could get so complex. Thanks for your suggestion.

[Richard-S]

We are testing and most of the problems seem to be caused by program logic and changes that caused something else to break. The update process is only replacing 4 fields in one record at a time so using a query seems to work, so far. I've also been told that using an unbound form might help so I'm going to see how that works vs. what I have now. Thanks.

[ItsMe]

I briefly mentioned using an unbound form. However, it does not seem one approach is going to address all issues. As you are discovering, there are many moving parts that depend on each other. Change one aspect and it can introduce new issues.

[Richard-S]

I briefly mentioned using an unbound form. However, it does not seem one approach is going to address all issues. As you are discovering, there are many moving parts that depend on each other. Change one aspect and it can introduce new issues.

I find this is going to be a discovery adventure. But it is worthwhile learning new complexities. Thanks again for your help. So far, the program seems to work pretty well.