Jump to content

Value Lists versus "Setup page" and DBs


Blake Lucas
 Share

This topic is 4316 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Hi All,

Ok.. I want to make my new database easy for admins to add/remove value lists as products change or grow.

Typically, I would just make Value Lists and enter in values there, but for future use, they are tough to edit add/remove items as things change, So this time I am making a "setup" layout that they can enter in values via portals of common items that can then be used later as value lists.

My dilema is that I have roughly 20 values lists I would like to create.. so do I make 20 databases with the list items for each, or one database with all the value fields for everything and then in the setup page, just filter the records to those with the data I am seeking?

Does that make sense at all. Let me know everyones thoughts... maybe I am over thinking this or there is an easier way to do this.

Thanks,

blake

Link to comment
Share on other sites

I am not sure I understand your purpose. Typically, "as products change or grow" is reflected in the Products table - and the value list is defined to show values from fields in that table.

If you have value lists that do not justify a table of their own, you can authorize users (or some users) to modify them (or some of them).

Link to comment
Share on other sites

This topic is 4316 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.