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

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

Recommended Posts

Posted (edited)

I found several discussions that touch on this topic but remain somewhat confused by the process, so here goes. I am developing an mass email function and have programmed a script to shut down the mailing should the messages fail to be sent. I would like to be able to see which messages, contained in an "Out" table have been sent and unsent so that resuming the email process will not result in any omissions or duplicate mailings.

My question: is it better to simply have a toggle field for each record (sent/unsent) or to move each sent message to a new table and delete it from the Out Table? Although I really don't want to dilute this post, I would like to know how one goes about pushing this data to a new table without actually go back and forth between the two (there must be a better way.)

I'd appreciate any suggestions on this matter.

Edited by Guest
Posted

is it better to simply have a toggle field for each record (sent/unsent) or to move each sent message to a new table and delete it from the Out Table?

What do you think is fastest, to move an entire record to a new table or to change the relational key so it pops up in a different portal??? Toggle fields or flagging fields are not my cup of tea, while alterations to the keyfield are more likley be endorsed by me.

What should the point be in pushing to another table if it isn't in a another releated files table. If a file goes down beyond repair could there though be a point in shifting it to several files tables preferably hosted on separate computers.

--sd

Posted

I'd toggle that Status field (it can be used as a relational key in filtered relationships.)

In general, it's best to keep like-data together in the same table. If you start moving records around, you increase the chance for data loss, and introduce syncronization issues.

Posted (edited)

Thanks Søren and Ender. I see your point and thanks for bringing the concept of filtered portals to my attention. Now that you mention it, I can't see any good reason to copy this data into a new table.

Edited by Guest

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