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

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

Recommended Posts

  • Newbies
Posted

Help ... I have a sales processing system that creates quotes which are then accepted. If a quote is accepted I need to be able to stop ANY UPDATE TO ANY FIELD including adding/deleting portal rows in a quote items table.

Any Ideas :??

Best Regards,

Peter

Posted

Hi Peter

You can use the preview mode under the view menu or in the layout mode under the edit menu select "select all" and then under the format menu goto field format and under behavior uncheck allow entry into field. do this where you want to view quotes that are accepted.

Lionel

  • Newbies
Posted

Dear Lional,

Many thanks for your response.

However, the table contains both accepted and unaccepted quotes.

The unaccepted quotes are allowed modifiable but the accepted quotes are to be

unmodifiable. Therefore it depends on the status of the record being viewed as to whether fields are modifiable.

Many thanks,

Peter

Posted

Hi Peter

Make another db and import the accepted quotes into it and then delete them from the original db.

do a search for accepted quote

import to second db

delete found set

show all record

this way you have a db that has only acceptable quotes and you can show it in the preview mode.

You could also do a find for acceptable quotes in the original db and show it in the preview mode but that would still let someone change records by just opening the db and browse throuht it.

hope this helps

Lionel

Posted

Hi,

You could use a 'validate by calculation' option for any field appearing in this portal. Using 'strict 'with 'message' will prompt the user to abort the modification.

There's a drawback though...

You can create a new portal row. But you won't be able to enter data in it. This will lead you to an "empty" related record. But you can use a script to delete this empty record.

Think of a second file too as suggested by Lionel... I can't see any need for the import procedure though if this second file is an "Order.db". This would be solved by a relational design including an extra table (join file) to join the quotes and orders together (or not)...

  • 5 months later...
Posted

I just found this so I thought I would pop my 2 cents in. Use validate by calculation, Create a text field in your database called Edit. Set that field to yes on record creation, make it not modifable. What ever fields you want to "lock" down set the validation to edit=yes. Make a button for the user to hit "Order Accepted". This fires off a script that set edit to no. Fields can not be changed. I have a sample file if anyone is interested in this.

  • 1 year later...
Posted

I just found this so I thought I would pop my 2 cents in. Use validate by calculation, Create a text field in your database called Edit. Set that field to yes on record creation, make it not modifable. What ever fields you want to "lock" down set the validation to edit=yes. Make a button for the user to hit "Order Accepted". This fires off a script that set edit to no. Fields can not be changed. I have a sample file if anyone is interested in this.

Ken,

Any chance on getting a FMP6 version of this example?

Thanks,

Richard

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