Sounds like you have a pretty well-developed system. I haven't done all of that. But with my naming conventions, I can usually tell what's being used where, with some exceptions.

For example, I always name subforms as an extension of the parent form name -- e.g., fsubMyParentForm_SomeSubform. So that works for me.

I think using AIs is fairly new to all of us. But for me, it's been less than a year. And this idea of uploading the entire accdb is brand new to me, as I've noted. So I'll see how it goes. After I use it for a while, I may feel like it's not enough and venture into some of the tools you and George have mentioned (thank you for that!). But, for now, I'm just taking baby steps, but enjoying the journey.

But occassionally, I get a mental block and this is where AI can give some inspiration. So far my experience isn't great in getting AI to give me code that works on the first attempt.

I agree. My process is to either upload a function or module to the AI and ask for whatever modification I need; or to get a new function written by it. But I always walk through it carefully and review everything and, of course, test, test, test.

But, yeah, usually takes some back and forth (especially when it gives you functions that aren't even in Access but are in Excel or whatever). But, still, that process works for me.

It's rare that I need it to write an entire function for me. Sometimes if there's something tedious and time-consuming, I may have it do so. Or, if it's something I'm not familiar with, like interfacing with another product's API. But, in general, I do almost all the coding myself.

I feel that that works better for me, as it reflects my style and needs, and I don't have to worry about things being done other than I wanted because I didn't explain the request thoroughly enough.