Looping an OnError until duplicate error clears.

[Keithg1229]

Ok, this may not even be possible, but I have to ask if anyone can think of anything. Searches have come up empty.

What I am trying to do in a form is after updating a customerID field, the next field CustomerEntry# populates with a 1. Easy enough.

The issue is that these 2 #'s combined form a unique ID in the table, so I want to make it so if the runtime error for duplicates comes up, it goes to the error handler and adds one to the value, then rechecks for duplicates again, and if the error occurs, try again, etc until there is no duplicate anymore.

Because the duplicate is in the table, not the form, I need to refresh the form to get the desired error. I have successfully got it to loop through once, changing the answer to 2, but after that the OnError doesn't seem to work and the error pops up with the form refreshes again.

I appreciate any ideas people might have. I'm a novice with OCD which is a bad combo ;) After 3 hours of failing I decided to stop trying and seek advice. Thanks to all.

[PhilOfWalton]

Please let us see your table structure. It doesn't look too good.

Phil

[Keithg1229]

The database is at work I will have to wait a few days. Thanks for getting back. The table is a bear I created it years back when I had no idea what I was doing.

[NeoPa]

KeithG:
I'm a novice with OCD which is a bad combo ;)

On the contrary. Software and database design is a perfect fit for OCD!

In this case you may want to consider checking the table first to determine what is the maximum value already in use. Here's (Item Numbering Within a Group) an article that points the way. A different, but quite similar, use case shouldn't put you off. Let us know if you struggle with it.

OTOH. With reference to re-using OnError code ever, it helps to understand that once an error has triggered this code, the error state is such that it knows it's in an error state. That is, until any form of Resume is used.

So, Resume or Resume Next will allow the OnError statement to be re-instated. Using any other way to loop through to your code will ensure it is still in error mode so the OnError won't be active. I hope that makes sense.

[Keithg1229]

Thanks so much, I will read this linked info and give it a whirl. Also thanks for the info about On Error I did not know that!

[Keithg1229]

Ok I came up with a completely different way to do this using DCount and an unbound text field that equals the ID# for the criteria.

Thanks guys for getting back to me :)

[NeoPa]

Hi Keith.

That approach (if I understand you correctly) will work up to a point. It does assume that none of the records are missing from the list and that all existing records within the specified grouping are numbered sequentially from one to the maximum number used.

In my experience that is not a safe thing to rely on. DMax() does a much more reliable job for you.

Good thinking though ;-)

[Keithg1229]

I didn't think to try that. I will play around with it. Thanks for the suggestions :)

[NeoPa]

KeithG:
I didn't think to try that.

It was at the heart of the article I linked to in post #4. If you haven't read that yet I recommend you do. There are a number of gotchas involved that it will help you avoid.

Good luck.