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

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

Recommended Posts

Posted

I need to create a system that is easy to use, consistent in look-n-feel, and

at least the layout and table defs are reasonably easy to maintain -- in a

very large multi-table, multiple target-audience, data mining application (in

this case, dozens of tables but only tens of thousands of records).

To keep maintenance reasonably possible for not-so-techie people, I want to

give them single layouts for each table, and then many other layouts specific

to search tasks. The single layouts bit is what keeps this from being an easy

task; but without single layouts the length of time before the application

becomes inconsitant is shortened considerably (someone who only uses some

"views" of a record may not update the lesser/non-used views).

I think my needs are:

1: one-to-many relationships

2: single layout must support the one-side record's add/edit/delete/find, 

	and a portal to the many-side record

3: the many-side portal does not show all fields

4: single layout must support the many-side record's add/edit/delete/find.

If I want to do this with buttons for each record, I need to be able to show/hide those buttons through scripts. How can I do this??

Posted

I need to create a system that is easy to use, consistent in look-n-feel, and

at least the layout and table defs are reasonably easy to maintain -- in a

very large multi-table, multiple target-audience, data mining application (in

this case, dozens of tables but only tens of thousands of records).

To keep maintenance reasonably possible for not-so-techie people, I want to

give them single layouts for each table, and then many other layouts specific

to search tasks. The single layouts bit is what keeps this from being an easy

task; but without single layouts the length of time before the application

becomes inconsitant is shortened considerably (someone who only uses some

"views" of a record may not update the lesser/non-used views).

I think my needs are:

1: one-to-many relationships

2: single layout must support the one-side record's add/edit/delete/find, 

	and a portal to the many-side record

3: the many-side portal does not show all fields

4: single layout must support the many-side record's add/edit/delete/find.

If I want to do this with buttons for each record, I need to be able to show/hide those buttons through scripts. How can I do this??

Posted

I need to create a system that is easy to use, consistent in look-n-feel, and

at least the layout and table defs are reasonably easy to maintain -- in a

very large multi-table, multiple target-audience, data mining application (in

this case, dozens of tables but only tens of thousands of records).

To keep maintenance reasonably possible for not-so-techie people, I want to

give them single layouts for each table, and then many other layouts specific

to search tasks. The single layouts bit is what keeps this from being an easy

task; but without single layouts the length of time before the application

becomes inconsitant is shortened considerably (someone who only uses some

"views" of a record may not update the lesser/non-used views).

I think my needs are:

1: one-to-many relationships

2: single layout must support the one-side record's add/edit/delete/find, 

	and a portal to the many-side record

3: the many-side portal does not show all fields

4: single layout must support the many-side record's add/edit/delete/find.

If I want to do this with buttons for each record, I need to be able to show/hide those buttons through scripts. How can I do this??

Posted

You can use portals to hold your buttons. The portals use a self-relationship. You scripts sets the value of one of the keys. If the relationship is good the portal and button show, if it is bad they disappear. Use a transparent line for the portal.

Posted

You can use portals to hold your buttons. The portals use a self-relationship. You scripts sets the value of one of the keys. If the relationship is good the portal and button show, if it is bad they disappear. Use a transparent line for the portal.

Posted

You can use portals to hold your buttons. The portals use a self-relationship. You scripts sets the value of one of the keys. If the relationship is good the portal and button show, if it is bad they disappear. Use a transparent line for the portal.

Posted

I'm sorry, but I'm not clear .. exactly anyways:

In the portal view from a layout to the many record, add a portal using a self-relationship containing only my buttons. If the many portal has a matching record, it's key value will be set, so the self-portal will show.

What's this transparency bit? I think I know why you say it .. in a layout with a portal with the screen elements remain hidden. So? -- if I set aside space for the buttons and set the fill to transparent and line to transparent it will not appear to show? Yeah! I think I just figured that one out smile.gif

Thank you! Looks like a beautifully simple method!

Posted

I'm sorry, but I'm not clear .. exactly anyways:

In the portal view from a layout to the many record, add a portal using a self-relationship containing only my buttons. If the many portal has a matching record, it's key value will be set, so the self-portal will show.

What's this transparency bit? I think I know why you say it .. in a layout with a portal with the screen elements remain hidden. So? -- if I set aside space for the buttons and set the fill to transparent and line to transparent it will not appear to show? Yeah! I think I just figured that one out smile.gif

Thank you! Looks like a beautifully simple method!

Posted

I'm sorry, but I'm not clear .. exactly anyways:

In the portal view from a layout to the many record, add a portal using a self-relationship containing only my buttons. If the many portal has a matching record, it's key value will be set, so the self-portal will show.

What's this transparency bit? I think I know why you say it .. in a layout with a portal with the screen elements remain hidden. So? -- if I set aside space for the buttons and set the fill to transparent and line to transparent it will not appear to show? Yeah! I think I just figured that one out smile.gif

Thank you! Looks like a beautifully simple method!

This topic is 7203 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.