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

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

Recommended Posts

Posted

I'm trying to find the best way to keep a set of newly created records the focus of future actions. The particulars: I have a database tracking rental properties in our city. The inspector needs to send a batch of letters regarding properties that are due an inspection. The inspector will add anywhere from 1 to a few hundred new letters at a given time, and then need to view and print just those letters.

I have a script that successfully creates a new batch of letters from the current found set, and creates these child records in a seperate table, referenced by the key "license #." Each letter has a serial #.

It seems like I could approach this with a variation on the "restore found set" technique, or create a portal that filters the records, based upon a global that I create within the "create letters" script.

This seems to be a key function in my solution, and I am early on in the development - I want to head down the best path. It is very likely that there are other options, but I'm not advanced enough with FM to know all of my options.

Any suggestions would be greatly appreciated!

Posted

If letters always need to be approved

You could add either a boolean or a date field that is set after the letter has been approved and printed. This would easily allow you to find all records that are NOT approved.

If they don't always need to be approved

You could create some sort of record selection feature. Have a boolean is_Selected field that you can set via a checkbox for a single record, or set/clear for an entire found set at once. This would be used to create an ad hoc record set. Again, you could easily search via this field.

Posted

If letters always need to be approved

You could add either a boolean or a date field that is set after the letter has been approved and printed. This would easily allow you to find all records that are NOT approved.

If they don't always need to be approved

You could create some sort of record selection feature. Have a boolean is_Selected field that you can set via a checkbox for a single record, or set/clear for an entire found set at once. This would be used to create an ad hoc record set. Again, you could easily search via this field.

These seem like good, clean solutuions. Thanks!

Any suggestion on the easiest way to set/clear on a found set? Loop/go to next record/set field/exit when done...that kinda thing?

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