Also Pete, I understand splitting, I have done it in the past. That's not the problem.
The big problem will be getting family members to manage a FE and a BE. I know that a single file is easier to work with than two.
Today, if I send folks 10 tables, 30 forms, and 20 reports to copy into BE and FE files, it won't get done. And if I send folks 30 tables tomorrow and 50 forms tomorrow, all I will hear will be crickets. You may say 10/30/20 and 30/50 is a lot, but I create lots of objects when I read textbooks, magazine articles, and research on the Web. Sorry about that.
The 550 forms in my database now could grow to 1000 in four months. The number of tables and reports may also double in number.
Some developers on AW tag me for not having a normalized database. But so far, no one has told me how to create DKNF tables. I see 3NF in the literature, but why should I leave holes in my database structure when I can do DKNF? That makes no sense to me.
Another problem is that no one knows how structured my database really is. They haven't seen the relationship map or used the database. They don't know what calculations it does and why. They have not listened to it talk. They have not used the graphics. I keep describing parts of the database, but it will take a thousand pages of text to do the application justice.
What should I do folks? I am inclined to continue creating tables, forms, and reports. The forms and reports need to have speech, graphics, and animation. Are there enhancements beyond that that I can make?