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

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

Recommended Posts

  • Newbies
Posted

I have 3 related databases. One is an alphabetical listing of teachers and the keys they carry. The second is a listing of the hook numbers (which is stamped on the key) and which rooms they operate. The third is an archive of who had which key in a previous year.

The problem - There are times in my alphabetical database when the same key number is issued out to 2 different people. So, I

Posted

I'm not sure which part of that is creating problems for you.

It sounds like you know how to find duplicates.

It sounds like you intend to manually look at the duplicates and decide which one to send to the archive file. Right?

Then you'll have a button that says "Archive" (or whatever)... and it will create a new record in the Archive file, populate it with the contents from the current record, and then delete the current record. I am guessing that you know how to script that. True?

Then, is the question: how do I delete the current record without losing my place in the found duplicates? Have you tried just experimenting with it by doing a find and then just deleting one of the records, manually? I suspect the default behavior will work for you.

Thus, its not clear to me where you need help. What's the question?

Posted

An efficient way to create the additional record in your archive file would be to ensure that you have a relationship between the alphabetical file and the archive file which is based on a unique key field in the alphabetical file (eg serial# or recordID) and that the relationship has the options to "Allow creation of related records" enabled.

Then if you attach a script to your button which has a series of "Set Field" steps to write data from each of the fields in the alhabetic file (except the unique key field) to the archive file (based on the unique key relationship), a record will be created in the archive file which matches the current record (if one doesn't alreay exist - if one does exist it will be updated with the current information from the alphabetical file.

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