Your current database is in terrible shape. Even the form that should work has suffered from VB corruption (the module is cut off). After deleting all lines that do not compile and adding the missing End Sub after the last Sub, all I can say is that the form behaves very badly.

After fixing all the obvious problems, I played with the form a little (being constantly nagged by a popup asking for a photo). I added a new control (to check the number after it: it was above 1000), and that alone made the form crash again. I suspect you have already passed the limit.

Basically, you have too many controls, and your code is too long.

> The tabs have an on change event that changes the query that works as the datasource.

That is a horrible idea. You should *never* change the Record Source of a form. It's sometimes a neat trick for simple forms, but it's a certain road to VB corruption in most cases. Instead, your Tab 2 should have one single control: a subform. Let that subform have the alternate source you need for it.

In fact, it would be best if each tab was a subform. You could even break down the first page into several pages for better performance.

As for the VB coding, it's highly redundant. The after update and click events are very similar; you should create simple modular code for them (as global functions or as class modules). As it stands, it's not manageable anyway.

Forgive me for saying so, but you might want to hire an Access specialist for this. I'm guessing that the table structure itself needs improvement. Your data isn't in normal form, which makes any database operation -- including creating this form -- very difficult. Several areas (all those with numbered controls) should be sub-forms, taking their data from a linked table.

I know this isn't what you wanted to read, but there is really nothing I or another expert can do through EE. This needs a complete rewrite from scratch, starting with the table structure.

(°v°)