Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

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

Recommended Posts

  • Newbies
Posted

i don't mean this in the simple sense of defining a field to repeat so many times... i already have that. What i am trying to do, is have a user define how many times he/she needs to have a field repeat.

Printing company... going through a job spec. they need to define options for the 'job part'(cover, text, etc.) each 'job part' has the same options through the a value list. So, i have a field next to the field name 'job part' where the user can input a number, 3 for example, and that will define how many repeating fields occur under the 'job part' field. does that make sense??

i have been through one very mediocre book, and one much more extensive book, neither go into this idea. i have killed 2 days attempting to grasp how to script this seemingly simple task with no luck. any suggestions will be greatly appreciated.

Posted

This is *exactly* the situation where you don't use repeating fields, you use a portal and related records instead.

Relational has the ultimate flexiblity -- as many or as few rows (related records) as you like.

The portal interface is easy to work with. Users don't even need to know it's a related file they just keep adding rows to the portal.

  • Newbies
Posted

thanks Vaughan. i'll get back into it right now. i'll have to do a little re-planning and focus more on the use of portals. keep your eyes out!!! i'll probably be back.

thanks again

michael

This topic is 7957 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
×
×
  • Create New...

Important Information

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