FM7 Layouts

[Jalz]

Hi Guys,

I'm asking for advice for a fairly simple problem. My FORM screen has about 30 fields which the user can alter at will.

The problem is, the altering at will (as the multiusers are changing fields and then not realising it!), is there a way where I can have my FORM screen so that users can "view" data (so the FORM would not allow any data entry), however when they want to edit data, i'd like them to click on an edit button, which will allow entry into fields.

At present with FM6, I do this with two layouts, Layout1 is readonly, and Layout2 is not. when you click on the edit button, it takes you to layout2. Is there a more efficient way of doing this with FMP7, as Im about to rewrite my solution and I find the current method quite clunky.

If there are any sample files with one or two fields in FP7 format that someone could allow me to view would be great.

Have any of your users, complained about how easy it is to edit/change data without realising it?

[Jalz]

Hi Guys,

I'm asking for advice for a fairly simple problem. My FORM screen has about 30 fields which the user can alter at will.

The problem is, the altering at will (as the multiusers are changing fields and then not realising it!), is there a way where I can have my FORM screen so that users can "view" data (so the FORM would not allow any data entry), however when they want to edit data, i'd like them to click on an edit button, which will allow entry into fields.

At present with FM6, I do this with two layouts, Layout1 is readonly, and Layout2 is not. when you click on the edit button, it takes you to layout2. Is there a more efficient way of doing this with FMP7, as Im about to rewrite my solution and I find the current method quite clunky.

If there are any sample files with one or two fields in FP7 format that someone could allow me to view would be great.

Have any of your users, complained about how easy it is to edit/change data without realising it?

[Jalz]

Hi Guys,

I'm asking for advice for a fairly simple problem. My FORM screen has about 30 fields which the user can alter at will.

The problem is, the altering at will (as the multiusers are changing fields and then not realising it!), is there a way where I can have my FORM screen so that users can "view" data (so the FORM would not allow any data entry), however when they want to edit data, i'd like them to click on an edit button, which will allow entry into fields.

At present with FM6, I do this with two layouts, Layout1 is readonly, and Layout2 is not. when you click on the edit button, it takes you to layout2. Is there a more efficient way of doing this with FMP7, as Im about to rewrite my solution and I find the current method quite clunky.

If there are any sample files with one or two fields in FP7 format that someone could allow me to view would be great.

Have any of your users, complained about how easy it is to edit/change data without realising it?

[Zadkin]

I used in v6 the 'limiting access on a record-by-record basis' option to make the edition of a record dependent of

- a global status field (view or edit state)

- record status field (record locked as it is an audit trail, or only modifiable by a specific user)

- layout ( backdoor to the previous, the record is locked but the administrator can still 'solve problems')

The use of a limited access based on a global status field could be your answer.

[Zadkin]

I used in v6 the 'limiting access on a record-by-record basis' option to make the edition of a record dependent of

- a global status field (view or edit state)

- record status field (record locked as it is an audit trail, or only modifiable by a specific user)

- layout ( backdoor to the previous, the record is locked but the administrator can still 'solve problems')

The use of a limited access based on a global status field could be your answer.

[Zadkin]

I used in v6 the 'limiting access on a record-by-record basis' option to make the edition of a record dependent of

- a global status field (view or edit state)

- record status field (record locked as it is an audit trail, or only modifiable by a specific user)

- layout ( backdoor to the previous, the record is locked but the administrator can still 'solve problems')

The use of a limited access based on a global status field could be your answer.

[Jalz]

Thanks Zadkin,

I think this may be the answer. I have a calculation underneath Edit Records; Limited option. My calc is Global_Edit ="Edit". This allows me to edit records, if the value Edit is in my global_edit field. If its not, it comes up with an annoying error message, "this field is not modifiable", any chance i can put up my own error message?

Can you eloborate why I would need point (3) from your last post - "layout ( backdoor to the previous, the record is locked but the administrator can still 'solve problems')"

Thanks

[Jalz]

Thanks Zadkin,

I think this may be the answer. I have a calculation underneath Edit Records; Limited option. My calc is Global_Edit ="Edit". This allows me to edit records, if the value Edit is in my global_edit field. If its not, it comes up with an annoying error message, "this field is not modifiable", any chance i can put up my own error message?

Can you eloborate why I would need point (3) from your last post - "layout ( backdoor to the previous, the record is locked but the administrator can still 'solve problems')"

Thanks

[Jalz]

Thanks Zadkin,

I think this may be the answer. I have a calculation underneath Edit Records; Limited option. My calc is Global_Edit ="Edit". This allows me to edit records, if the value Edit is in my global_edit field. If its not, it comes up with an annoying error message, "this field is not modifiable", any chance i can put up my own error message?

Can you eloborate why I would need point (3) from your last post - "layout ( backdoor to the previous, the record is locked but the administrator can still 'solve problems')"

Thanks

[Zadkin]

Point 3 is not usefull in your case. I used it when I locked down individual records, besed on a status record on record level. By attributing the record to one specific user for example or in a definitive frozen state. In an administrative layout the records where still editable and the status could be changed to a more editable state.

[Zadkin]

Point 3 is not usefull in your case. I used it when I locked down individual records, besed on a status record on record level. By attributing the record to one specific user for example or in a definitive frozen state. In an administrative layout the records where still editable and the status could be changed to a more editable state.

[Zadkin]

Point 3 is not usefull in your case. I used it when I locked down individual records, besed on a status record on record level. By attributing the record to one specific user for example or in a definitive frozen state. In an administrative layout the records where still editable and the status could be changed to a more editable state.

[Jalz]

I see, I understand now.

Any chance of editing the error message to a more useful message, or is that just not possible with the current version?

Thanks for your help. I think I can use your suggestion quite effectively.

[Jalz]

I see, I understand now.

Any chance of editing the error message to a more useful message, or is that just not possible with the current version?

Thanks for your help. I think I can use your suggestion quite effectively.

[Jalz]

I see, I understand now.

Any chance of editing the error message to a more useful message, or is that just not possible with the current version?

Thanks for your help. I think I can use your suggestion quite effectively.