Letting the user select the table, in which they want to add/edit records

[Sniper-BoOyA-]

Good Morning,

I was wondering if it was possible to let the user select a table, in which he/she need to add or edit a record.

The reason is as follows:

I am making a database to determine the relationship between Regulatory Requirements and Standards used in our branche sector.

Sometimes the Standards change, and in order to get a good view on what documents are refering to the standard(s) in question, i want to make a database in which u can either search by the name of the Regulatory Requirements or the Standards.

Anyways,

I am currently working on a form, that gives the user the opportunity to add/edit records in the table. And instead of having to make 10 different forms, i was wondering if it was possible to make 1 form (with subform?) and give the user the option to select the table he wants to add records to.

Is that possible?

Cheers!!

 

[Galaxiom]

Subforms have different record sources. Each subform can be connected to a different table.

 

[vbaInet]

I think you're seeking a rapid development process and cutting back on functionality. If you're happy with using the Datasheet View for all forms then GalaxiomAtHome's suggestion is one possibility.

If the Link Master Fields and/or Link Child Fields properties are different then changing the Source Object would be the way to go. That is, if the subform is meant to be bound to the parent form. Then obviously you would change those two properties accordingly.

 

[Sniper-BoOyA-]

Subforms have different record sources. Each subform can be connected to a different table.

Thats what i thought.. thanks for the confirmation

 

[Sniper-BoOyA-]

I think you're seeking a rapid development process and cutting back on functionality. If you're happy with using the Datasheet View for all forms then GalaxiomAtHome's suggestion is one possibility.

If the Link Master Fields and/or Link Child Fields properties are different then changing the Source Object would be the way to go. That is, if the subform is meant to be bound to the parent form. Then obviously you would change those two properties accordingly.

Its not really a rapid development process i want, its more that i want to be able to do as much in one form, and not having to change forms.

But then again, if it cuts back on the funtionality of the application, then obviously its better to make seperate forms after all.

I am just doing a little bit of brainstorming at this point.

 

[vbaInet]

I am just doing a little bit of brainstorming at this point.

Certainly the best way to go about things before getting your hands dirty

Its not really a rapid development process i want, its more that i want to be able to do as much in one form, and not having to change forms.

It would be a good idea to create one form, make all the design changes and use that as a template for the other forms.

But then again, if it cuts back on the funtionality of the application, then obviously its better to make seperate forms after all.

You may not want to do any coding now but in the future you may need greater flexibility and without having separate forms, you won't be able to do much. So you might as well develop it in such a way that it is robust.

Happy developing!

 

[Sniper-BoOyA-]

It would be a good idea to create one form, make all the design changes and use that as a template for the other forms.

I ended up doing just that. Just made all the forms. Now i need to make a form with a search function.

Cheers for your help!

 

[vbaInet]

Good job Sniper!