Modify form on accde database

No.  You cannot make changes to forms, reports, or code modules in an accde file.

you have to do the changes in the .accdb version, (if you have the .accdb version ) then create an .accde version

Hi Jim - thank you (and thank you also Dale and Rey),

Whilst I know you're pretty much always spot on, I am curious as to why the data model would be off.  

There could be 100 projects each with a different set of questions.  95% of the database would be the same on each project (i.e. forms, tables and functionality - all the same).  I just need a place to display the fields specific to each project (the back-end will be changed also so there would still be 100 back-end databases).  So, I'm not sure if I'm missing something that would make my life easier.

Thanks again guys.

Andy,

 The reason I said that is that you've modeled a database for "a project", and yet you need to change the form design when entering different instances of "a project".   With the right design, that shouldn't need to happen.

There are of course always exceptions.   An asset tracking model is one that is tough to wrap your arms around because each asset may have wildly different attributes, all of which you might want to track (say disk space in a PC, vs whether a desk is a stand up or sit down model).   That's where a hybrid design with an EAV setup tacked on can be helpful.

<<I just need a place to display the fields specific to each project (the back-end will be changed also so there would still be 100 back-end databases). >>

  and there's the rub; you should have one back end, with one set of tables and just more records in each when you add another project.  The structure and design of the DB and app should not need to change in order to simply add new projects.

<<So, I'm not sure if I'm missing something that would make my life easier.>>

  Without knowing more, it's hard to say, but an EAV design would probably help.

Jim.

Thanks Jim I'll take a look at EAV design and post another question if needed.

Take care,

Andy

Sadly Jim that design model won't work for me.

I need to keep each project in it's own separate database (as there will be different clients and sites using them).  For example I may have a client that uses the application for handling RSVP to an event, whilst another one might be a completely different company using it to book appointments for a sales team.  Also, each company may have several projects for different things (on the same site).  So to keep things simple, we simply provide them with one database for each project (all of the data is unique to each one anyway).  

In a perfect world, I would have one master Access database, and when the user selects the project that they are working on, it displays the project-specific fields (as well as all of the standard ones), links to the relevant back-end and off they go.  Ideally, I'd like the sub-form displaying the unique data to add the fields from a table containing the layout/controls etc.

Not sure if that makes sense....but hopefully it does.